![](https://secure.gravatar.com/avatar/41e7a39428c47f8fe4125d5b8e0f24bd.jpg?s=120&d=mm&r=g)
Could someone add a link to the info about how to join/participate to the README?
After following a detour via 'CONTRIBUTING', which would be a symlink locally, but just had a path printed inside on gitlab, I found a description here: https://gitlab.com/inkscape/inkscape/blob/master/doc/HACKING.txt
I think that file also needs an update, telling users *how* to 'request access' now that the option via button is closed.
(what would have been the issue with just declining any non-contributor join requests? Not being able to add an explanatory note? Perhaps make this a gitlab feature request?)
Maren
Am 14.01.2018 um 03:29 schrieb Bryce Harrington:
I've proceeded ahead and made this config change to gitlab. Let me know if anyone spots any issues with this change.
Bryce
On Sat, Jan 13, 2018 at 09:10:59AM -0800, Bryce Harrington wrote:
On Sat, Jan 13, 2018 at 09:32:03AM +0100, Marc Jeanmougin wrote:
No objection from me, sounds nice (I did not know we could remove the button^^); what I tried to do at some point was to give "Guest" role to those users (which does not grant any right)
I also wondered about establishing an Inkscape Users subgroup that people could voluntarily add themselves to. (This might be worth doing regardless, particularly if we have some utility for it beyond just affiliation.)
Bryce
On 01/13/2018 06:28 AM, Bryce Harrington wrote:
There's a setting "Allow users to request access" on our Inkscape main group (https://gitlab.com/inkscape). I'd like to switch it to 'off'. Are there any objections if I did this?
This setting adds a button to our website for logged in users to push to send an email to our admins asking for membership to the inkscape main group. The effect of this gives them commit access on the inkscape repo (and I suspect maybe other git repos in subgroups; I'm not sure how the permissions propagate.)
This was useful initially when everyone was needing gitlab access, but I think all the existing committers that want it have it. These days the requests we're getting are mostly from people with no registered activity related to Inkscape; we've been getting a handful of these invalid requests each month. Maybe they're clicking it on accident, or thinking that it's an affiliation mark, and not realizing that it gives full commit rights if granted.
Turning it off simply removes the button, it wouldn't mean any change to our existing policies regarding earning of commit rights - applicants still need to get two patches reviewed, accepted, and landed and then contact one of the administrators to request access. (If we want to make this simpler later on, maybe one day we can rig up a form where they can enter the SHAs of their two patches.)
Bryce
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel