ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

ChiliProject Security Mailing Lists (Task #37)

Added by Muntek Singh at 2010-12-29 11:06 am. Updated at 2011-01-29 08:35 pm.

Status:Closed Start date:2010-12-29
Priority:Normal Due date:
Assignee:Eric Davis % Done:

0%
Category:ChiliProject - Organization
Target version:Public Launch
Remote issue URL:

Description

Setup Security mailing lists

  • Shared inbox for archival purposes
  • Forward emails to the members of the Security Team
  • Email "admin" access for the Security Team leader to add/remove forwards

Related issues

related to Task #7: Public web site Closed
related to Task #52: Setup email accounts Closed 2011-01-12

History

#1
Updated by Eric Davis at 2011-01-02 06:28 pm

  • Target version deleted ()

#2
Updated by Eric Davis at 2011-01-12 01:58 pm

  • Category set to ChiliProject - Organization

#3
Updated by Eric Davis at 2011-01-12 02:29 pm

  • Tracker changed from Bug to Task

#4
Updated by Eric Davis at 2011-01-12 03:11 pm

  • Target version set to Public Launch

#5
Updated by Felix Schäfer at 2011-01-13 12:49 am

Hosted or one we setup? Should we go with the later, I suggest we use sympa, it's worked reliably for us for some time now, has a good feature-set and each user has a full account (no password-sharing like mailman x_X). I also believe it to be available in debian/ubuntu.

#6
Updated by Eric Davis at 2011-01-13 02:59 pm

I'd rather go hosted, we shouldn't need to run everything ourselves.

The Release mailing list (read only) can be something like Mailchimp (or even a dedicated blog RSS feed that is setup to deliver email).

The Security mailing list is the only one that needs to be read/write, but we can just use a dedicated email account and have mail forwarded to the security team.

#7
Updated by Eric Davis at 2011-01-13 03:41 pm

  • Subproject of deleted (#7)

#8
Updated by Eric Davis at 2011-01-13 03:41 pm

  • Subject changed from Mailing Lists to ChiliProject Mailing Lists

#9
Updated by Holger Just at 2011-01-15 07:16 am

I think, we could handle both use cases on Google (with the groups feature). Although for the announce list (and probably additional general mailinglists) we might have to test the user experience for the general audience first.

#10
Updated by Muntek Singh at 2011-01-15 08:09 am

Is there a built-in way to allow users to subscribe to gapps groups? Last I checked there was not.

#11
Updated by Felix Schäfer at 2011-01-15 08:15 am

I'm not sure what you mean, if you mean "subscribe without a google ID": possible, but not at the click of a button (see here), though there seem to exist a variety of ready-made boxes where people can just enter an address and hit go to get subscribed (see here for example).

#12
Updated by Eric Davis at 2011-01-16 01:19 pm

What about just using Feedburner's email system for a release mailing list? We can hook it upto any RSS feed and either:

  1. Have a dedicated "Release" feed on the blog.
  2. Use the News module's ATOM feed (would send out more than releases though).
  3. Or write something custom for releases. They are so infrequent we can do thing manually for a bit with a CRUD plugin and toss it into an RSS feed.

#13
Updated by Felix Schäfer at 2011-01-16 03:04 pm

Eric Davis wrote:

What about just using Feedburner's email system for a release mailing list?

Don't know if I said it already, but I don't care much as long as it works :-)

We can hook it upto any RSS feed and either:

  1. Have a dedicated "Release" feed on the blog.
  2. Use the News module's ATOM feed (would send out more than releases though).

Should we use the news module if running an external blog? Either we use the only the external blog, use a common tag for releases and use that through feedburner, or use the news section for releases only, pipe the ATOM to feedburner and use the blog for everything else.

#14
Updated by Eric Davis at 2011-01-16 03:37 pm

Felix Schäfer wrote:

Should we use the news module if running an external blog? Either we use the only the external blog, use a common tag for releases and use that through feedburner, or use the news section for releases only, pipe the ATOM to feedburner and use the blog for everything else.

Good question. Personally I think the News module is very weak, so maybe that could be used for releases only? Then the news module could be:

"Version X has been released, see the release notes on the blog for more details"

#15
Updated by Felix Schäfer at 2011-01-16 03:44 pm

I could even live with not using the news section at all, but that would be fine too, listing the 2-3 main changes wouldn't hurt though.

#16
Updated by Eric Davis at 2011-01-17 03:56 pm

Lets just focus on the security mailing list for now. The releases one can be figured out later on.

I've updated the description with the requirements, who has access to the Google email admin account?

  • Subject changed from ChiliProject Mailing Lists to ChiliProject Security Mailing Lists

#17
Updated by Eric Davis at 2011-01-20 11:06 pm

The security mailing list has been setup and tested.

  • Assignee set to Eric Davis
  • Status set to Closed

#18
Updated by Muntek Singh at 2011-01-29 08:35 pm

Eric Davis wrote:

Felix Schäfer wrote:

Should we use the news module if running an external blog? Either we use the only the external blog, use a common tag for releases and use that through feedburner, or use the news section for releases only, pipe the ATOM to feedburner and use the blog for everything else.

Good question. Personally I think the News module is very weak, so maybe that could be used for releases only? Then the news module could be:

"Version X has been released, see the release notes on the blog for more details"

I vote get rid of the new module entirely, and only use the blog. You can put all the release announcements into one category and we can link to it from several places. Wordpress will automatically generate the rss feeds for categories, for example: http://blog.chiliproject.org/category/community/feed/ which we can use for the mailing list or for anything else. The news module is pretty anemic compared to wordpress in every way, I'll reiterate my choice to get rid of it and use the blog for everything.

Also available in: Atom PDF