Re: [DISCUSS] Creating additional lists for announcements and JIRA
On Mon, Jan 7, 2019 at 4:16 PM Mike Jumper wrote: > On Mon, Jan 7, 2019 at 4:04 PM Nick Couchman wrote: > >> On Mon, Jan 7, 2019 at 17:38 Mike Jumper >> >> > > >> > > I'll also use this opportunity to ping on the topic of resurrecting >> the >> > > Guacamole Twitter account - any further thoughts/discussion on this? >> > > >> > >> > I think the main issue with Twitter is that there can be only one set of >> > credentials. AFAIK, we can't have a project account to which various >> people >> > have permission to post without sharing a username/password. Other than >> > that, I would have nothing against a project Twitter account, though I'm >> > not sure I would find occasion to post to it except at release time. I >> do >> > see other Apache projects with a PMC-wide twitter, so it should be >> > doable... >> > >> > Are you familiar with any way to share a Twitter account without having >> to >> > share credentials? >> > >> >> Admittedly, no, I don't know if a great way to do this. I did stumble >> across this: >> >> https://help.twitter.com/en/using-twitter/tweetdeck-teams >> >> Looks like it may be doable there, and we'd just have to have someone be >> the primary account holder and hold the credentials, and that person could >> grant access to others? > > > Since I'm the one with the credentials to the old account, I can give that > a shot. > > I'll also try to rename from @GuacDev to something like @ApacheGuacamole. > All set: https://twitter.com/ApacheGuacamole Since granting access to tweetdeck requires Twitter accounts, I'll send a separate email on private@ to ask for usernames of any PMC members having accounts. - Mike
Re: [DISCUSS] Creating additional lists for announcements and JIRA
On Mon, Jan 7, 2019 at 4:04 PM Nick Couchman wrote: > On Mon, Jan 7, 2019 at 17:38 Mike Jumper > > > > > > > I'll also use this opportunity to ping on the topic of resurrecting the > > > Guacamole Twitter account - any further thoughts/discussion on this? > > > > > > > I think the main issue with Twitter is that there can be only one set of > > credentials. AFAIK, we can't have a project account to which various > people > > have permission to post without sharing a username/password. Other than > > that, I would have nothing against a project Twitter account, though I'm > > not sure I would find occasion to post to it except at release time. I do > > see other Apache projects with a PMC-wide twitter, so it should be > > doable... > > > > Are you familiar with any way to share a Twitter account without having > to > > share credentials? > > > > Admittedly, no, I don't know if a great way to do this. I did stumble > across this: > > https://help.twitter.com/en/using-twitter/tweetdeck-teams > > Looks like it may be doable there, and we'd just have to have someone be > the primary account holder and hold the credentials, and that person could > grant access to others? Since I'm the one with the credentials to the old account, I can give that a shot. I'll also try to rename from @GuacDev to something like @ApacheGuacamole. - Mike
Re: [DISCUSS] Creating additional lists for announcements and JIRA
On Mon, Jan 7, 2019 at 17:38 Mike Jumper > > > > I'll also use this opportunity to ping on the topic of resurrecting the > > Guacamole Twitter account - any further thoughts/discussion on this? > > > > I think the main issue with Twitter is that there can be only one set of > credentials. AFAIK, we can't have a project account to which various people > have permission to post without sharing a username/password. Other than > that, I would have nothing against a project Twitter account, though I'm > not sure I would find occasion to post to it except at release time. I do > see other Apache projects with a PMC-wide twitter, so it should be > doable... > > Are you familiar with any way to share a Twitter account without having to > share credentials? > Admittedly, no, I don't know if a great way to do this. I did stumble across this: https://help.twitter.com/en/using-twitter/tweetdeck-teams Looks like it may be doable there, and we'd just have to have someone be the primary account holder and hold the credentials, and that person could grant access to others? -Nick > >
Re: [DISCUSS] Creating additional lists for announcements and JIRA
On Mon, Jan 7, 2019 at 2:38 PM Mike Jumper wrote: > On Mon, Jan 7, 2019 at 2:20 PM Nick Couchman wrote: > >> On Mon, Jan 7, 2019 at 4:33 PM Mike Jumper wrote: >> >> > It occurs to me that it might be beneficial to have a low-traffic >> announce@ >> > list for Guacamole which would receive only things like release >> > announcements or security advisories. >> > >> ... > > > >> > Similarly, JIRA issues and comments currently go to commits@. Perhaps a >> > separate issues@ list would be more appropriate, leaving commits@ for >> > truly >> > only pushed git commits? >> > >> >> This is probably a good idea, too. Concurrently, I'd like to make sure >> I'm >> on both the commits@ and issues@ lists - I'm not 100% certain I get >> either >> JIRA issues or pushed commits at the moment, unless I'm tagged on them >> specifically. >> > > I'll move ahead with creating the lists and see how things go. > > Alrighty - creation of the issues@ list has been queued. Once the list is ready, I'll open a ticket with Infra to update the JIRA project to send all mail there. Since the announce@ list needs special setup (only posts from apache.org addresses should be allowed), I've opened a ticket with Infra for that: https://issues.apache.org/jira/browse/INFRA-17578 - Mike
Re: [DISCUSS] Creating additional lists for announcements and JIRA
On Mon, Jan 7, 2019 at 2:20 PM Nick Couchman wrote: > On Mon, Jan 7, 2019 at 4:33 PM Mike Jumper wrote: > > > It occurs to me that it might be beneficial to have a low-traffic > announce@ > > list for Guacamole which would receive only things like release > > announcements or security advisories. > > > > Sounds good to me. I'm hoping this year will see an increase in number of > release (and, thus, release traffic) with the adoption of the new > versioning scheme :-D. > > I'll also use this opportunity to ping on the topic of resurrecting the > Guacamole Twitter account - any further thoughts/discussion on this? > I think the main issue with Twitter is that there can be only one set of credentials. AFAIK, we can't have a project account to which various people have permission to post without sharing a username/password. Other than that, I would have nothing against a project Twitter account, though I'm not sure I would find occasion to post to it except at release time. I do see other Apache projects with a PMC-wide twitter, so it should be doable... Are you familiar with any way to share a Twitter account without having to share credentials? > > > > Similarly, JIRA issues and comments currently go to commits@. Perhaps a > > separate issues@ list would be more appropriate, leaving commits@ for > > truly > > only pushed git commits? > > > > This is probably a good idea, too. Concurrently, I'd like to make sure I'm > on both the commits@ and issues@ lists - I'm not 100% certain I get either > JIRA issues or pushed commits at the moment, unless I'm tagged on them > specifically. > I'll move ahead with creating the lists and see how things go. We should poke the other members of the PMC (as well as any non-PMC committers) to subscribe if not already subscribed. I can manually check to see who's missing. - Mike
Re: [DISCUSS] Creating additional lists for announcements and JIRA
On Mon, Jan 7, 2019 at 4:33 PM Mike Jumper wrote: > It occurs to me that it might be beneficial to have a low-traffic announce@ > list for Guacamole which would receive only things like release > announcements or security advisories. > Sounds good to me. I'm hoping this year will see an increase in number of release (and, thus, release traffic) with the adoption of the new versioning scheme :-D. I'll also use this opportunity to ping on the topic of resurrecting the Guacamole Twitter account - any further thoughts/discussion on this? > > Similarly, JIRA issues and comments currently go to commits@. Perhaps a > separate issues@ list would be more appropriate, leaving commits@ for > truly > only pushed git commits? > This is probably a good idea, too. Concurrently, I'd like to make sure I'm on both the commits@ and issues@ lists - I'm not 100% certain I get either JIRA issues or pushed commits at the moment, unless I'm tagged on them specifically. -Nick
[DISCUSS] Creating additional lists for announcements and JIRA
It occurs to me that it might be beneficial to have a low-traffic announce@ list for Guacamole which would receive only things like release announcements or security advisories. Similarly, JIRA issues and comments currently go to commits@. Perhaps a separate issues@ list would be more appropriate, leaving commits@ for truly only pushed git commits? Thoughts? - Mike
