Hi Tony! I’d sort of be in favor of eventually using option 3 since that would likely make life easier and faster in a number of situations when one is bursting with activity, and can avoid going somewhere else to look it up quick.
I’m not sure what process we’d use to make that decision (maybe the one Colin is drafting), but I think it’s reasonable that if you have an account and log in, you can find the emails for other project members. -Steve On Jul 17, 2014, at 8:12 PM, Tony Atkins <[email protected]> wrote: > Hi, Steves... :) > > I work on Thursday and Friday, so everyone got a bit longer grace period. I > just opened up the "browse users" permission, which should fix the original > concern Till reported. > > I did also hide our email address as originally proposed, but wanted to point > out the full range of options: > Email addresses can be visible to everyone (including bots). > Obfuscated addresses (tony at raisingthefloor dot org) can visible to > everyone (including bots). > Email addresses can be visible to people who are logged in. > Email addresses can be completely withheld from everyone. > As discussed last week, I have configured our JIRA instance for the fourth > option. People can share issues with each other by using "at mentions" in > comments, or by using the "share" function on the top right side of the issue > view, but will not see each other's email addresses. > > I can see moving to option 3 if we feel that not having addresses is stifling > communication at all. The other two seem more like a privacy violation to > me. > > In any case, we can change at any time, I say we live with it for a week or > two and comment here if there are concerns or problems. > > Cheers, > > > Tony > > > On Thu, Jul 17, 2014 at 7:42 AM, Steve Lee <[email protected]> wrote: > I also offer a late +1 and wonder if you made the change? > > Steve Lee > OpenDirective http://opendirective.com > > > On 14 July 2014 15:06, Steven Githens <[email protected]> wrote: > Hi Tony, > > This sounds great. Did you make the change? ( I’m a dev so I’m not sure I > would have noticed it not happening ). > > -Steve > > > On Jul 10, 2014, at 10:11 PM, Tony Atkins <[email protected]> wrote: > >> Hi, All: >> >> Till pointed out recently that it's very difficult to involve people in >> issues using shares and mentions, because of the way our JIRA instance is >> configured: >> >> http://issues.gpii.net/browse/GPII-869 >> >> Right now, we only allow our developers to see the list of users on our JIRA >> instance, which means that only developers can easily share tickets using >> the built in share and "at mention" mechanisms. >> >> I would propose opening this up so that people can more easily involve other >> members of the community who we have not set up as developers in our >> instance. This seems much more in keeping with our overall philosophy of >> inclusion. >> >> The only small concern is that the "browse user" permission allows users to >> see each other's email address. If this is a concern at all, I would >> propose configuring JIRA to not show email addresses. It will still be >> possible to share content with other users through mentions and shares. >> >> The model is similar to LinkedIn, where you only know the user's LinkedIn >> credentials and they can choose whether to share anything further with you. >> >> I am putting this out for discussion today. If there are no objections by >> close of business tomorrow, I will go ahead and allow all JIRA users to see >> other users and hide user email addresses in JIRA. Each change is easily >> reversible if there are any concerns or we choose to do things differently. >> >> Cheers, >> >> >> Tony >> _______________________________________________ >> Architecture mailing list >> [email protected] >> http://lists.gpii.net/cgi-bin/mailman/listinfo/architecture > > > _______________________________________________ > Architecture mailing list > [email protected] > http://lists.gpii.net/cgi-bin/mailman/listinfo/architecture > > >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
