THe press@ address should point to the Marketing and Comms team leader (marcomm) is currently one team with two functions). I'm the current leader, hoping that this can be in place before Mageia 1 Release Day to catch press enquiries and to send out release-related informationto wherever we need it sent. If the press@ address is already delivering to board or council - and they don't want it to change - could there be a communications@ address instead, just for outgoing comms from Mageia? At some point we'd like there to be multiple addresses available to the team, but it's kind of small yet. However, if there's a right way (TM) to plan for that, it would be good to know.
CC: (none) => trish
There is already a press@ alias, and also a mageia-contact@ list ( that is spammed quite often ). In order to manage this more cleanly, I would need to create a group for communication team in ldap to track leader and members, but for that, I need the member list. In the mean time, you should see with people in the alias ( rda, ennael, colin, wobo and dams ) to manage the change of owner. Personnaly, I think this should go to someone of the comm team, but in order to not lose mail, especially from press, we should have more than 1 person to answer and read this alias. Regarding aliases login@mgeia for the team, it is up to the team, the only requests is that 1) people must have a identity account 2) people must be in a group for that 3) aliases should be distributed to people who did work rather than " I am volunteer, ok, here is your aliases", as people using this will be seen as officialy representing the project. The rest s up to the team.
CC: (none) => misc
okay - passed back to rda (raising this as a bug was his suggestion).
Yes, he asked for aliases so I said that a bug should be opened but I didn't understood it was press@ aliases.
Ok, let's put this in order: * we need a communication (call it "communication") group/team setup in LDAP * Patricia is this team's leader * she needs a trish@mageia.org alias * she decides who gets into that team - I am not sure there are other than volunteers so far, but that's up to Patricia to name team peers (who would get an alias) As for the press@ address; I am not sure if we should setup a shared IMAP box or keep it as an alias. If we keep it as such: * I suggest press@ alias sends to all people in the communication team; objection to that? * if so, I would like to be in this team as well - and other board members would ask for that as well if they want to follow this alias * note that this is strictly separate from subscriptions to the marcom mailing-list (mageia-marketing@mageia.org). mageia-contact@ should be kept as it is for now, that's a separate issue. As I am not sure anymore whether we should formally separate marketing and communication, I suggest we use this communication group so far, and see later.
CC: (none) => rdalverny
(In reply to comment #4) > As for the press@ address [...] Note that incoming messages into press@ are not necessarily in English, so readers should expect that.
For press being sent to all communication team, wouldn't mean that the communication team will be "small", and kinda restricted like sysadmins ( ie, people we trust ) ? This is fine by me, but may have side effect ( ie, is the blog a duty of communication team, so should we count blog people as part of this team ? ). If we use communication team to provides access to some part of the system ( like access to blog, to various ublog account, etc ), we may have then to create another subteams and separate thing a little bit more. So here is what I propose to do now : - I add trish on the alias on ryu for the time being ( we will clean it after the release ) - I create the group in ldap, with trish as owner - I let people in the council have aliases ( so by side effect, trish will have the aliases ) We ponder on what the communication team manage ( think blog, ublog, and various access, but also if custom software should be needed ) and if additional subgroup are needed, how the team could evolve , etc. ( like communication, communication-press, communication-ublog, communication-blog ) Once the distribution is out and dust settle : - we move people from the alias to the communication team and remove it from zarb.org server to our own - we decide who have a aliases for the team, etc.
(In reply to comment #6) > For press being sent to all communication team, wouldn't mean that the > communication team will be "small", and kinda restricted like sysadmins ( ie, > people we trust ) ? Why should it be restricted? Press inquiries/info is not/should not be confidential. Those joining the communication team anyway are to be people we do have a minimum of trust for :-) > This is fine by me, but may have side effect ( ie, is the blog a duty of > communication team, so should we count blog people as part of this team ? ). If > we use communication team to provides access to some part of the system ( like > access to blog, to various ublog account, etc ), we may have then to create > another subteams and separate thing a little bit more. So far, I would keep it decoupled, and let people organize themselves. Team is too small/young for now. > - I add trish on the alias on ryu for the time being ( we will clean it after > the release ) > - I create the group in ldap, with trish as owner > - I let people in the council have aliases ( so by side effect, trish will > have the aliases ) > > We ponder [...] Sounds good yes.
I heard story about people in the communication business were quite secretive of their addressbook, so since the addressbook is basically just a collection of email/etc, it made sense to me to treat such data as private. Now, if there is no issue with that, that's ok for me too. Regarding the blog/ublog, etc, the issue is the lack of representation in the council, ie for now, they exist outside of the planned structure, and IMHO, that should be addressed sooner or later ( and obviously, that would be later rather than sooner )
(In reply to comment #8) > I heard story about people in the communication business were quite secretive > of their addressbook, so since the addressbook is basically just a collection > of email/etc, it made sense to me to treat such data as private. Now, if there > is no issue with that, that's ok for me too. The secrecy is the other way around. People pinging directly the press@ alias doesn't make them open to alternative topics, furthermore, if ever, most contacts belonging to a "secret personal addressbook" won't be reached through this alias, but in a 1-to-1 discussion. > Regarding the blog/ublog, etc, the issue is the lack of representation in the > council, ie for now, they exist outside of the planned structure, and IMHO, > that should be addressed sooner or later ( and obviously, that would be later > rather than sooner ) blog/ublog/etc. resorts on the communication team in the end, but this is still mostly managed by founders & board so far. One way or the other, these are in the Council.
(In reply to comment #8) > > Regarding the blog/ublog, etc, the issue is the lack of representation in the > council, ie for now, they exist outside of the planned structure, and IMHO, > that should be addressed sooner or later ( and obviously, that would be later > rather than sooner ) What would the role of blog team ? I think blog can be managed by people from different teams : - sysadmin team: installing blog - web team: customizing blog - i18n: translating posts from english to other languages - communication team: writting blog posts
The role of the blog team would be to have access at the blog, so if everybody is already from another team ( which is not evident now ), then it would be ok for me. ( on a technical point of view, I would also like to have blog plugged to ldap as this would ease the user management, but this is likely not gonna happen soon ). So I added trishf42@mageia to the alias press@mageia, added the proper config for the @mageia.org aliases, and created the group with trish and romain as member.
(In reply to comment #11) .................... > > So I added trishf42@mageia to the alias press@mageia, added the proper config > for the @mageia.org aliases, and created the group with trish and romain as > member. Everybody happy and this bug solved?
CC: (none) => marja11
yes - I'm getting press@ emails just fine, thanks!
Marking it solved.
Status: NEW => RESOLVEDResolution: (none) => FIXED