It depends how you classify me. I consider myself as a non-developer but I can tolerate if developer status is needed for editing the wiki when updating GSIP votes, for example.
-Jukka-
···
Lähettäjä: Justin Deoliveira [mailto:jdeolive@…3839…] Lähetetty: 12. kesäkuuta 2014 4:15 Vastaanottaja: Jody Garnett Kopio:geoserver-devel@lists.sourceforge.net; Andrea Aime Aihe: Re: [Geoserver-devel] Testing transition to wfs-ng
And how often do folks that aren’t developers edit the wiki? My impression is not often. I am thinking it is not often enough to justify going against the norm.
On Wed, Jun 11, 2014 at 5:25 PM, Jody Garnett <jody.garnett@…403…> wrote:
The only reason to keep it associated with the website is so we have the option of allowing commit access to more people.
Jody Garnett
On Thu, Jun 12, 2014 at 1:29 AM, Justin Deoliveira <jdeolive@…3839…> wrote:
On Wed, Jun 11, 2014 at 9:13 AM, Andrea Aime <andrea.aime@…1268…> wrote:
On Wed, Jun 11, 2014 at 5:11 PM, Justin Deoliveira <jdeolive@…3839…> wrote:
Except that is not exactly our release schedule, it’s the old description of it (previous to the last GSIP)
Cool, i am on it, Unless anyone objects I would like to have the wiki attached to the geoserver wik be the one we use. So I was going to also port the content from the geoserver.github.io wiki there as well.
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
It is okay Jukka, wiki is migrated lets get on with it. I would like to nominate Jukka for commit access for docs, website and wiki
Assuming the nominiation is successful, can you send me your github id? I may ask you to fill in the “new” code contribution agreement assuming that GSIP goes ahead…
It depends how you classify me. I consider myself as a non-developer but I can tolerate if developer status is needed for editing the wiki when updating GSIP votes, for example.
And how often do folks that aren’t developers edit the wiki? My impression is not often. I am thinking it is not often enough to justify going against the norm.
Cool, i am on it, Unless anyone objects I would like to have the wiki attached to the geoserver wik be the one we use. So I was going to also port the content from the geoserver.github.io wiki there as well.
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
Sorry, I mis-spoke on this one, i meant to say how often do folks who don’t have commit access edit the wiki. And Jukka I definitely think you quality for commit access
However, as it turns out wiki access in a public repo is available to anyone with a github account, they don’t have to be part of the organization or have push rights to the repository.
You can however restrict this so if we wanted to we could create a new team of collaborators that don’t have push access to the repo, and restrict wiki access to just collaborators.
It depends how you classify me. I consider myself as a non-developer but I can tolerate if developer status is needed for editing the wiki when updating GSIP votes, for example.
And how often do folks that aren’t developers edit the wiki? My impression is not often. I am thinking it is not often enough to justify going against the norm.
Cool, i am on it, Unless anyone objects I would like to have the wiki attached to the geoserver wik be the one we use. So I was going to also port the content from the geoserver.github.io wiki there as well.
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
On Thu, Jun 12, 2014 at 4:59 PM, Justin Deoliveira <
jdeolive@anonymised.com> wrote:
Sorry, I mis-spoke on this one, i meant to say how often do folks who
don't have commit access edit the wiki. And Jukka I definitely think you
quality for commit access
However, as it turns out wiki access in a public repo is available to
anyone with a github account, they don't have to be part of the
organization or have push rights to the repository.
You can however restrict this so if we wanted to we could create a new
team of collaborators that don't have push access to the repo, and restrict
wiki access to just collaborators.
Interesting... hmm... the confluence wiki was sort of open and it became a
mess, wondering if we should close the github one in a similar way.
Do we get notifications is someone edits the pages?
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information.
Ing. Andrea Aime @geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
On Thu, Jun 12, 2014 at 9:04 AM, Andrea Aime <andrea.aime@anonymised.com>
wrote:
On Thu, Jun 12, 2014 at 4:59 PM, Justin Deoliveira <
jdeolive@anonymised.com> wrote:
Sorry, I mis-spoke on this one, i meant to say how often do folks who
don't have commit access edit the wiki. And Jukka I definitely think you
quality for commit access
However, as it turns out wiki access in a public repo is available to
anyone with a github account, they don't have to be part of the
organization or have push rights to the repository.
You can however restrict this so if we wanted to we could create a new
team of collaborators that don't have push access to the repo, and restrict
wiki access to just collaborators.
Interesting... hmm... the confluence wiki was sort of open and it became a
mess, wondering if we should close the github one in a similar way.
Not sure it is that necessary. I think github has figured out how to block
automated spam, unlike our old confluence setup where the mess resulted
from scripts being able to set up new accounts.
Also one of the great things about being able to access the wiki as a
repostory is that it will be trivial to roll back or filter out any spam
commits we don't want.
Do we get notifications is someone edits the pages?
I don't believe so. Although a quick search yields that you can set up
service hooks for the wiki repository the same way as the regular
repository, so probably possible.
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information.
Ing. Andrea Aime @geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
