jasig-dev email list
- Andrew Petro
- Aaron Godert
Several members of the JA-SIG community /wiki/spaces/JCH/pages/103735480 to discuss our overall status of email lists for JA-SIG. We decided to use the jasig-discuss for this list's purpose, so for the time being we will not create this list. However, if we decide that the jasig-discuss isn't cutting for the the needs listing below, then we will create this list and split out the purposes of the lists.
This page represents a proposed email list
List creation metadata
Initial subscriber set
This would be a meta-list across the developer lists of all JA-SIG projects.
Is approval required to join the list? If so, who are the list admins?
No individuals should join this list itself – membership is through membership in a particular project's developer list.
Who can post to the list?
Members of any JA-SIG project's developer list.
Is the list moderated?
Not until it needs to be.
Is the list archived? For how long? Are the archives public?
The list archives should be public and retained "forever".
Can subscribe requests be made via email? Do they require approval?
No individual can subscribe.
Should reply-to go to the poster or to the whole list?
Reply-to should go to the original poster to help people take care in what they send to this broad meta-list.
What is the description of the list?
Discussion of issues in developing JA-SIG projects that go beyond an individual project yet are specific to JA-SIG (rather than about Java programming generally).
Should the list name be pre-pended to the subject?
Yes, [jasig-dev] should be prepended to the subject.
Why do we need this list?
The idea for this list was perhaps first raised here.
What would be discussed on this list
- Developer resource outages (version control most notably, but Hypercontent as well)
- JA-SIG version control practices
- Procedures for posting JA-SIG project release binaries
- Using Hypercontent to manage JA-SIG project web presences
There have been occasions in the past where announcements sent to jasig-dev have had to be echoed to cas-dev because jasig-dev is not in fact a cross-project developer list, it is as you rightly point out actually used as a uPortal developer list.
I wouldn't expect jasig-project-dev to be a high traffic list, but I think there are occasions where there's something to announce or discuss about developing JA-SIG projects.