Awesome, thanks Paul.
Note to all devs: if you want your contributions to CouchDB to show up
on your GitHub profile, you have to star each of the repositories.
(That's just how GitHub mechanics work for repo mirrors.)
You can find them all here:
https://github.com/apache
On 17 January 2014
Psst. A little birdy tells me that if you ask nicely, the infra folks
will add you to the Apache GitHub org too, so you can show off your
Apache affiliation. I was the first person added. Because I may have
been the first to ask. ;)
On 17 January 2014 11:56, Noah Slater nsla...@apache.org wrote:
I'm claiming 2nd person added!
On 17 Jan 2014, at 1:28 PM, Noah Slater nsla...@apache.org wrote:
Psst. A little birdy tells me that if you ask nicely, the infra folks
will add you to the Apache GitHub org too, so you can show off your
Apache affiliation. I was the first person added. Because
Might I suggest that this sounds like good info to document on the wiki
for committers getting started. I'd add it but I'm not in the allow-list.
:)
/JamesM
On 1/17/14 4:00 AM, Garren Smith gar...@apache.org wrote:
I'm claiming 2nd person added!
On 17 Jan 2014, at 1:28 PM, Noah Slater
Good plan. What's your wiki username? I'll add you.
On 17 January 2014 20:01, Mutton, James jmut...@akamai.com wrote:
Might I suggest that this sounds like good info to document on the wiki
for committers getting started. I'd add it but I'm not in the allow-list.
:)
/JamesM
On 1/17/14
JamesMutton
/JamesM
On 1/17/14 11:09 AM, Noah Slater nsla...@apache.org wrote:
Good plan. What's your wiki username? I'll add you.
On 17 January 2014 20:01, Mutton, James jmut...@akamai.com wrote:
Might I suggest that this sounds like good info to document on the wiki
for committers
Excellent! Done, thanks.
/JamesM
On 1/17/14 11:44 AM, Noah Slater nsla...@apache.org wrote:
Done. Edit away! (Thanks!)
On 17 January 2014 20:28, Mutton, James jmut...@akamai.com wrote:
JamesMutton
/JamesM
On 1/17/14 11:09 AM, Noah Slater nsla...@apache.org wrote:
Good plan. What's
It doesn't appear that this is objectionable to anyone. Does anyone
have an objection to us having infra/me create these repos to use for
the bigcouch/rcouch merge work? This won't affect master or releases
until those merges finish.
On Tue, Jan 14, 2014 at 11:02 PM, Paul J Davis
+1 go for it Paul.
I was wondering if the namespace is important -- e.g. will you rename
jiffy to couch_jiffy (or whatever) so that it can be hosted at
git://git.apache.org/couchdb-jiffy.git ?
or would it be better to put them at e.g.
git://git.couchdb.apache.org/jiffy.git or any other more
For the time being they have to be prefixed with couchdb- because of
the git hosting infrastructure. Other than that I was planning on just
being programatic in the naming to be something like couchdb- +
reponame.replace(_, -).
This does have the effect of making repo names like
On 16 Jan 2014, at 20:42 , Paul Davis paul.joseph.da...@gmail.com wrote:
It doesn't appear that this is objectionable to anyone. Does anyone
have an objection to us having infra/me create these repos to use for
the bigcouch/rcouch merge work? This won't affect master or releases
until those
Infrastructure ticket opened: https://issues.apache.org/jira/browse/INFRA-7203
On Thu, Jan 16, 2014 at 1:42 PM, Jan Lehnardt j...@apache.org wrote:
On 16 Jan 2014, at 20:42 , Paul Davis paul.joseph.da...@gmail.com wrote:
It doesn't appear that this is objectionable to anyone. Does anyone
New repos are up: https://git-wip-us.apache.org/repos/asf?s=couchdb
I'm gonna go through and initialize them with history from master or
one of the bigcouch and rcouch branches as appropriate.
On Thu, Jan 16, 2014 at 2:12 PM, Paul Davis paul.joseph.da...@gmail.com wrote:
Infrastructure ticket
On Jan 14, 2014, at 3:22 PM, Paul Davis paul.joseph.da...@gmail.com wrote:
I'd like to propose that we move to having a repository for each
application/dependency that we use to build CouchDB. Each repository would be
hosted on ASF infra and mirrored to GitHub as expected.
Good idea. It's
+1. The monolithic design makes development and pull requests easier, one
vs many for some features, but I think this is generally outweighed by the
pros outlined. I think a broken-out design makes it easier to add
alternate functionality in places, or swap in/out things to test with.
I agree
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis paul.joseph.da...@gmail.comwrote:
I've recently been having discussions about how to handle the
repository configuration for various bits of CouchDB post-merge. The
work that Benoit has been doing on the rcouch merge branch have also
touched on
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis paul.joseph.da...@gmail.comwrote:
I would also point out that even though our main repo would need to
fetch other dependencies from the internet to build the final output,
we fully intend that our release tarballs would *not* have this
On Jan 14, 2014, at 8:47 PM, Benoit Chesneau bchesn...@gmail.com wrote:
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis
paul.joseph.da...@gmail.comwrote:
I would also point out that even though our main repo would need to
fetch other dependencies from the internet to build the final
On Jan 14, 2014, at 8:37 PM, Benoit Chesneau bchesn...@gmail.com wrote:
On Wed, Jan 15, 2014 at 12:22 AM, Paul Davis
paul.joseph.da...@gmail.comwrote:
I've recently been having discussions about how to handle the
repository configuration for various bits of CouchDB post-merge. The
19 matches
Mail list logo
