Issue 580 - Create allfeatures@openoffice.org
Summary: Create allfeatures@openoffice.org
Status: CLOSED DUPLICATE of issue 1408
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL: http://www.openoffice.org/www-discuss...
Keywords:
Depends on: 599
Blocks: 1622
  Show dependency tree
 
Reported: 2001-03-21 10:57 UTC by stx123
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2001-03-21 10:57:16 UTC
Please create a new mailing list allfeatures@openoffice.org.
All messages send to the project specific lists features@<project> should appear
additionally in this list (similar to allbugs or allcvs).
Comment 1 Unknown 2001-03-21 18:47:35 UTC
assigning to myself
Comment 2 Unknown 2001-03-21 18:47:49 UTC
accepting
Comment 3 Unknown 2001-03-24 00:42:08 UTC
list created but unable to add subscribers or moderators; see Issue #599

this task is now blocked by #599
Comment 4 Unknown 2001-03-27 00:16:54 UTC
edk,

I would like to consult with you on the best way to create this list.  
  a) subscribe each features@project.openoffice.org list by hand
  b) have you do it some other way

I ask becase i note that allcvs and allbugs are not made like (a)
Comment 5 Unknown 2001-03-27 16:08:00 UTC
So -- the mailing list exists (which took some work, because it required dealing
with local hacks done long ago).  The next step is somewhat complicated.

allbugs and allcvs are done with special mechanisms : NPM added in ways that IZ
and CVS resp. can be told to always cc those addresses.  Mail to the features
list -- this is just sent out when people want to discuss something, right?

The mechanism which ezmlm provides is sublists: this will require manual
subscription of each new -features list to the allfeatures list.  Further,
because our UI doesn't support sublists currently, it will mean no one can edit
allfeatures via the admin UI.  There is another approach, but I'm ambivalent
about it and don't want to put it out into production just yet.

So long as the restriction on using the admin UI to modify allfeatures is
alright, that's what I'll implement... at this point, I don't think I can offer
a solution which doesn't require manual subscription of new lists.
Comment 6 stx123 2001-03-27 16:23:22 UTC
I understand that adding new features@<projects> has to be done manually. OK,
we will lean to live with that :-)
WHat's about subscribing? Can they be added with the Admin UI?
Comment 7 Unknown 2001-04-20 21:01:29 UTC
It will be possible to do the subscriptions through the UI.  The part which
isn't possible that way is making these sublists : for that, the file
DIR/sublist should be created (in this case, DIR == ~tigrisq/allfeatures) --
that file should be empty, but it must exist.  It should be owned by tigrisq.

After that, you can subscribe all the other lists ... 
Comment 8 Unknown 2001-07-13 18:56:34 UTC
Goolie's technical issues go to David.

-jh-
Comment 9 Unknown 2001-07-16 15:40:16 UTC
i accept this issue and will look into it.  i don't have the history on   
this issue so i'm not sure if this will be something that gets fixed in   
the upcoming upgrade or not.  i'll look into this and report back.
Comment 10 Unknown 2001-09-05 01:04:52 UTC
Dupe of 1408.

*** This issue has been marked as a duplicate of 1408 ***
Comment 11 michael.bemmer 2003-03-11 17:29:55 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 12 michael.bemmer 2003-03-11 17:57:57 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.