*Greetings Everyone!* * * Many important changes have been made to the OpenShot LaunchPad<https://launchpad.net/openshot>organization tonight. I have listed the changes below. Please let me know if you have any questions, complaints, suggestions, etc... We have already discussed most of these changes, so they shouldn't come as a surprise (hopefully). =)
- I have subscribed the "bug email" to our new "*OpenShot Bugs*" team ( [email protected]) - I have also changed the "Bug Supervisor" to the "*OpenShot Bugs*" team - I have added the following users to the "*OpenShot Bugs*" team, but everyone is invited to join that team<https://launchpad.net/~openshot.bugs/+members#active> : - Andy Finch - Cenwen - John Volk - Jonathan Thomas - moimael - So basically, all bug related communication will no longer happen on the *openshot.developers *mailing list, but rather the new *openshot.bugs *mailing list. This will give everyone more flexibility on how they organize and arrange their email to deal with bugs vs regular team communication. - I have deleted the "*OpenShot Users*" team, since it overlapped with our forums. - The Bazaar trunk for OpenShot is now owned by the "*OpenShot Code*" team. Only Andy and myself will be on this team (for now at least), and we now both have commit access to the main line of code. - The "*OpenShot Code*" team is now also the "security contact"... which was unset before. If any user checks the "Security Vulnerability" checkbox when submitting a bug, it will send us an email. Since this might be very sensitive, I figured it makes sense that less people would see these emails. I am very excited about the future direction of OpenShot, and I appreciate each of you so much for helping! The bigger we grow as a project, the more power and responsibility I will share. These changes are just the beginning. =) If I missed anything important, please let me know. Also, I have ordered a few very high quality black polo shirts, with the OpenShot logo embroidered on them. The same design I wore at SCALE 9X in California. They will be completed soon, and will be sent to Andy and Olivier first. I would love to buy everyone a shirt, but unfortunately they are very expensive, and I don't have the money right now. =( However, I promise to order more soon, and hopefully get them to all the people who help out the most! Thanks! -Jonathan On Wed, Jun 15, 2011 at 1:27 PM, Jonathan Thomas <[email protected]>wrote: > Hi Andy, > That is a great question. Would multiple teams stretch things a bit thin, > due to the low number of members we have... I still like 2 key aspects of > this approach though: > > 1. Moving all bug reports to a separate mailing list would de-clutter > our main channel of communication, which I really like. For example, in > Gmail I can tag the emails differently and make the tags different colors, > so I don't miss important emails. > 2. "OpenShot Code" would allow me to control commit access to our PPA > and Trunk, rather than granting all "Developers" that permission, which I > also really like. However, maybe there should be no mailing list > associated > with this team, as it would be used mostly for setting permissions. > > "OpenShot Users" could technically be deleted, as we already have a forum > to facilitate that type of communication. > > -Jonathan > > > On Wed, Jun 15, 2011 at 7:03 AM, Andy Finch <[email protected]>wrote: > >> I think it's a good idea in principal. Would enough members of the current >> team become active enough to split everyone out though? Despite having 25+ >> members of the team, only 3 or 4 ever seem to step up and participate in any >> way. >> >> On 15 June 2011 06:08, Jonathan Thomas <[email protected]> wrote: >> >>> A quick update for everyone. I have created the following teams & >>> mailing lists tonight on LaunchPad. I'm just thinking through the process >>> of how to best organize this stuff. Take a look: >>> >>> - *OpenShot Users:* https://launchpad.net/~openshot.users - General >>> user announcements, questions, discussions, etc... >>> - *OpenShot Code:* https://launchpad.net/~openshot.code - Only Bazaar >>> "committers" on the official OpenShot trunk. Very few developers in this >>> team (maybe 2 or 3). >>> - *OpenShot Bugs:* https://launchpad.net/~openshot.bugs - Receives >>> all bug-related emails and notifications. >>> - *OpenShot Developers:* https://launchpad.net/~openshot.developers (our >>> existing team) - Discussions about new features, updates, plans, >>> releases, >>> etc... Any developers welcome to this list. >>> >>> Please let me know thoughts, suggestions, complaints, or anything else on >>> your mind related to LaunchPad teams, mailing lists, organization, etc.... >>> >>> Thanks! >>> -Jonathan >>> >>> >>> On Tue, Jun 14, 2011 at 4:16 PM, Jonathan Thomas < >>> [email protected]> wrote: >>> >>>> Greetings everyone! >>>> >>>> I have been considering some changes to our LaunchPad team & mailing >>>> list structure for OpenShot, and I was hoping to get some good feedback on >>>> the following ideas. We currently only have a single team on LaunchPad, >>>> "OpenShot Developers". We use the same team as our "Bug Contact", which is >>>> why we all get so much email, etc... >>>> >>>> I would like to propose the following: >>>> >>>> - *OpenShot Developers* - This will be a general purpose team, to >>>> facilitate mailing list conversations on upcoming features, issues, and >>>> general communication. (similar to how it's used today) >>>> - *OpenShot Code* - This team will have commit access to our main >>>> code branch, and permissions to publish to the official PPA. Ideally, >>>> this >>>> will just be a very "select" and "small" group of our best developers. >>>> Currently I am the only developer with commit access, and I would like >>>> to >>>> at least grant this permission to another human, in case I get run over >>>> by a >>>> bus, or something. =) >>>> - *OpenShot Bugs* - This team is responsible for working bug >>>> reports, managing the bug system, and receiving the bug report emails. >>>> This >>>> mailing list will be the highest volume of email, compared to the other >>>> ones. >>>> >>>> So, there you have it. 3 LaunchPad teams w/ mailing lists, to better >>>> structure our group and communicate. Thoughts? Opinions? >>>> >>>> Another idea to better structure our teams, is to appoint people >>>> specific "titles" and "responsibilities" within the OpenShot organization. >>>> Think about that idea also, and let me know your ideas for positions / >>>> titles (and descriptions) that we might want to offer. Things like >>>> "Community Manager", etc... All of these ideas (new teams, new mailing >>>> lists, and new titles) are building towards a future where we are better >>>> organized, more informed, and more likely to survive the test of time. If >>>> one of us disappears, it would be nice to think the project could continue >>>> without too many surprises or problems. Just to clarify, I'm not planning >>>> on leaving the project at all. But, if I get run over or disappear for any >>>> reason, I want to ensure the survival of OpenShot, and all the great things >>>> we have built together. =) >>>> >>>> Thanks! >>>> -Jonathan >>>> >>>> >>>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openshot.developers >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~openshot.developers >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> >
_______________________________________________ Mailing list: https://launchpad.net/~openshot.developers Post to : [email protected] Unsubscribe : https://launchpad.net/~openshot.developers More help : https://help.launchpad.net/ListHelp
