couchapp merge &@
Benoit Chesneau
Sorry was a little too much busy these days to make the merge between
refactor branch & such. But I plan to do it this weekends. Apart of
that I would like to create a proper github project for that ie:
http://github.com/couchapp/couchapp/
rather than having :
http://github.com/benoitc/couchapp/tree/master
or
http://github.com/jchris/couchapp/tree/master
with differents commiters on this account. I think it would be better
for user to have a central point where they can report bugs, read the
wiki and follow latest devellopment. It also give a clear point to
see. Also, I think it would allow more contributions for the project
since there isn't any relation to one person in particular. What do
you think about it ?
- benoît
Andy Wenk
> Hi all,
>
> Sorry was a little too much busy these days to make the merge between
> refactor branch & such. But I plan to do it this weekends. Apart of
> that I would like to create a proper github project for that ie:
>
> http://github.com/couchapp/couchapp/
>
> rather than having :
>
> http://github.com/benoitc/couchapp/tree/master
> with differents commiters on this account. I think it would be better
> for user to have a central point where they can report bugs, read the
> wiki and follow latest devellopment. It also give a clear point to
> see. Also, I think it would allow more contributions for the project
> since there isn't any relation to one person in particular. What do
> you think about it ?
eventhough I do not commit code to the project, I think your
suggestion of having one place is a good one. +1 from me.
Maybe the couchapp project will become that big that it would be cool
to have a own website. But for now I don't know where and if it starts
to have to many places where we have things belonging to CouchDB.
Maybe a subdomain of www.couchdb.org ... but that's just "loud
thinking".
Greets
Andy
> - benoît
Chris Anderson
>
> On 14 Mai, 10:02, Benoit Chesneau <bchesn...@gmail.com> wrote:
>> Hi all,
>>
>> Sorry was a little too much busy these days to make the merge between
>> refactor branch & such. But I plan to do it this weekends. Apart of
>> that I would like to create a proper github project for that ie:
>>
>> http://github.com/couchapp/couchapp/
>>
>> rather than having :
>>
>> http://github.com/benoitc/couchapp/tree/master
>> orhttp://github.com/jchris/couchapp/tree/master
>>
>> with differents commiters on this account. I think it would be better
>> for user to have a central point where they can report bugs, read the
>> wiki and follow latest devellopment. It also give a clear point to
>> see. Also, I think it would allow more contributions for the project
>> since there isn't any relation to one person in particular. What do
>> you think about it ?
to distinguish between the JavaScript framework and the File System
Mapping. I keep hearing people say they don't want to use CouchApp
because all they want to do is manage some Map Reduce views, so maybe
there's a better way to make it clear that's *exactly* what it's for?
>
> Hi benoît,
>
> eventhough I do not commit code to the project, I think your
> suggestion of having one place is a good one. +1 from me.
>
> Maybe the couchapp project will become that big that it would be cool
> to have a own website. But for now I don't know where and if it starts
> to have to many places where we have things belonging to CouchDB.
> Maybe a subdomain of www.couchdb.org ... but that's just "loud
> thinking".
still room for that idea, but we haven't moved on it yet. The CouchDB
community would have to express an interest in that. If we want to do
it we'll have to speak up vocally on d...@couchdb.apache.org
Chris
>
> Greets
>
> Andy
>> - benoît
> >
>
--
Chris Anderson
http://jchrisa.net
http://couch.io
Benoit Chesneau
> I think this is a great idea!
Will do the move soon. I don't have any paid account on github though
(but have one on bitbucket) so we will be limited to 300Mo for start.
I'd also like to think harder about how
> to distinguish between the JavaScript framework and the File System
> Mapping. I keep hearing people say they don't want to use CouchApp
> because all they want to do is manage some Map Reduce views, so maybe
> there's a better way to make it clear that's *exactly* what it's for?
>
What's your idee ? On couchdbkit I've a system of loader that take any
design folders in one design and put design doc inside ie :
one folder/
design doc 1/
views ....
...
design doc 2/
....
Maybe it will be enough to add this to couchapp ? I'm thinking also to
improve the refactoring branch in a way to have complete file mapping
before anything else. So it could be used eventually by a fuse driver
or a webdav layer (or anything else).
>
> We talked about making it a CouchDB subproject, and I think there is
> still room for that idea, but we haven't moved on it yet. The CouchDB
> community would have to express an interest in that. If we want to do
> it we'll have to speak up vocally on d...@couchdb.apache.org
>
It could be propose also with some other idee like providing some
couchapp enhancements as a plugin to couchapp. For now I like the way
we could put new enhancements in couchapp faster than it could be in
an apache project but having couchapp as a subproject would provide
more lights on the project and maybe more contributions.
- benoit
Michael Frawley
I keep hearing people say they don't want to use CouchApp
because all they want to do is manage some Map Reduce views, so maybe
there's a better way to make it clear that's *exactly* what it's for?
Mike ˙∆˚
Benoit Chesneau
one design doc. For multiple design doc only couchdbkit allow it for
now. I will add this feature soon though.