[resent from apache.org address]
-Forwarded Message-
> From: Simon Kitching <[EMAIL PROTECTED]>
> To: community@apache.org
> Cc: general@incubator.apache.org, general@jakarta.apache.org,
> general@db.apache.org
> Subject: Re: Making Daffodil Replicator an Open Sourc
Ashish Srivastava wrote:
Hi,
We are a product based company named Daffodil Software Ltd, based in
India. We have developed many good products using JAVA out of which our
two premium product Daffodil DB (an RDBMS) and Daffodil Replicator
(database utility software) is largely accepted by world softw
Noel J. Bergman wrote, On 13/02/2003 21.14:
...
Pulling together all of the Committer information that already exists
*somewhere* on the ASF sites would be a major start. And once that is all
finished, it will be easier to see more of what is missing.
This is the conclusion we can to @ incubator.
> Agreed to a point. We don't have the tools that readily available
though...
What tools are you lacking? You check out the module, you edit the
contents, you submit patches via e-mail. If you want collaborative editing,
you use the Wiki to construct the content before [HTML|XML]-izing it.
> >
> > Community should be responsible for the pages and the content of the
> email.
>
> > Infrastructure are responsible for providing us with the tools to allow
> them
> > to be created/maintained etc.
>
> Those tools already exist. After being prepared, patches would be
submitted
> against the sit
> Community should be responsible for the pages and the content of the
email.
> Infrastructure are responsible for providing us with the tools to allow
them
> to be created/maintained etc.
Those tools already exist. After being prepared, patches would be submitted
against the site module, and se
> It thought it was a bit unhandy to dump part of the
> documentation on the Incubator site and part on www.apache.org/dev/.
Agreed. One or the other should be the repository for such content. The
point is to make it all available in a central place, not scattered like
chicken feed across the ya
> From: Justin Erenkrantz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 13, 2003 7:33 PM
> --On Thursday, February 13, 2003 1:12 PM -0500 "Noel J. Bergman"
> <[EMAIL PROTECTED]> wrote:
>
> > enough to do with keeping the plant running. The documents should
> > live in either Incubator (t
--On Thursday, February 13, 2003 1:12 PM -0500 "Noel J. Bergman"
<[EMAIL PROTECTED]> wrote:
enough to do with keeping the plant running. The documents should
live in either Incubator (to be provided to PMCs), or on the main
apache site.
The Incubator PMC has refused to add committer docs to thei
Community thing. The infrastructure guys have enough to do with
> keeping the plant running. The documents should live in either Incubator
> (to be provided to PMCs), or on the main apache site.
>
> --- Noel
>
> -Original Message-
> From: David Reid [mailto:[EMAIL
> True. I often pull new e-mail over to my notebook and read it on the
train.
> Not only that I won't follow links, I simply can't.
Have you tried marking pages for offline reading?
--- Noel
-
To unsubscribe, e-mail: [E
The documents should live in either Incubator
(to be provided to PMCs), or on the main apache site.
--- Noel
-Original Message-
From: David Reid [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 5:35
To: community@apache.org
Subject: Re: Suggestion...
I have a lot of sym
> > Perhaps, but I think we should make sure the "web page somewhere" part
> > doesn't get lost here. Read or not, the email will get deleted or lost
> > along the way. The web page provides a persistent location for this
> > information for new and old committers alike.
> >
> >
>
> Anakia (jakar
Rodney Waldhoff wrote:
(...)
Perhaps, but I think we should make sure the "web page somewhere" part
doesn't get lost here. Read or not, the email will get deleted or lost
along the way. The web page provides a persistent location for this
information for new and old committers alike.
Anakia (jak
On Thu, 13 Feb 2003, David Reid wrote:
> I have a lot of sympathy with that view, and it should probably be on a web
> page somewhere as well, but in all honesty getting an email with
> instructions makes it much easier than simply telling people to visit a web
> page. While we'd all like to think
> I have a lot of sympathy with that view, and it should probably be on a
> web
> page somewhere as well, but in all honesty getting an email with
> instructions makes it much easier than simply telling people to visit a
> web
> page. While we'd all like to think people would follow the link to the
I have a lot of sympathy with that view, and it should probably be on a web
page somewhere as well, but in all honesty getting an email with
instructions makes it much easier than simply telling people to visit a web
page. While we'd all like to think people would follow the link to the page
I thin
> There are clear instructions in the jakarta web site on how to handle
> cvs through ssh ...
This sort of information is scattered across the *.apache.org sites. There
are also instructions for doing it at
http://www.apache.org/dev/committers.html#general. Oddly there is a
separate section on C
Noel J. Bergman wrote:
David,
I agree that there should be an e-mail. But it should be short, and consist
of little more than a reference to the web site. All of this information
should be available on the web site for review and update. As that content
is enhanced, e-mail can go out to [EMAIL P
David,
I agree that there should be an e-mail. But it should be short, and consist
of little more than a reference to the web site. All of this information
should be available on the web site for review and update. As that content
is enhanced, e-mail can go out to [EMAIL PROTECTED]
> - forward
On Wednesday, February 12, 2003, at 02:12 PM, David Reid wrote:
an email that is automatically sent to new committers outlining the
"extra"
things that becoming a committer on an ASF project bring with them.
The aim
is to provide a sort of "Welcome to the ASF community" note.
I wonder if somethi
> I think it could/should contain things like
> - forwarding instructions for the @apache.org email address
> - contacts for common problems
> - information about the committers list and the reason for it
> - information on opt-in lists such as licensing, community
- A pointer towards instructions
David Reid wrote:
(...)
I think it could/should contain things like
- forwarding instructions for the @apache.org email address
- contacts for common problems
- information about the committers list and the reason for it
- information on opt-in lists such as licensing, community
If there are other
It was pointed out to me in a private email that one thing we don't do very
well is advertise the existence of things like this list to new committers!
We should change this at once :)
I'm not in favour of proposals being posted to this list, so please don't
vote on this!
- If you have nothing to
So, are you saying the boring repetitive 'news' from Commons is the
problem? Or just the acronym?
I'm all for adding a line to Commons releases which say what the project
is actually for :)
make the news explain what the significance of the release is and what
the heck CLI is. The news blurb
On Sat, 16 Nov 2002, Andrew C. Oliver wrote:
> Not meaning to embarrass anyone, but I suggest not writing "news" on any
> "news" pages like this:
>
> http://jakarta.apache.org/site/news.html#1106.1
>
> The Commons CLI team is proud to announce Commons CLI 1.0, the first
> official release of thi
CLI makes me think of Common Language Interface. Sure there
> are links but it might be just what someone who gets it in syndication
> needs, but they won't know based on this blurb and they'll rpobably miss it.
>
> Just a suggestion talk amongst yourselves...
That'
ut they won't know based on this blurb and they'll rpobably miss it.
Just a suggestion talk amongst yourselves...
28 matches
Mail list logo
