[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: hosting lua projects at github (was: lanes report error when script ends)
- From: Jim Whitehead II <jnwhiteh@...>
- Date: Mon, 3 Jan 2011 13:15:41 +0000
On Mon, Jan 3, 2011 at 1:13 PM, Benoit Germain <firstname.lastname@example.org> wrote:
>> -----Original Message-----
>> From: email@example.com [mailto:firstname.lastname@example.org]
>> On Behalf Of steve donovan
>> Sent: Monday, January 03, 2011 12:12 PM
>> To: Lua mailing list
>> Subject: Re: lanes report error when script ends
>> Good question! The idea is that people use whatever hosting they are
>> comfortable with, and we construct a catalog site of Lua projects.
>> LuaForge will remain viable as a catalog, but there are several holes
>> below the water line and it is slowly sinking.
> I got a quick peek at github. It seems that the directory structure starts at user level. For example, I could host Lanes at https://github.com/benoit.germain/lua-lanes.
> Now, what if the project changes hands? Is it stuck forever under directory benoit.germain, or can github transfer repository ownership in case someone else takes over project maintenance? If not, what about creating a special "lua" user under which all lua code repositories would be hosted? This particular user could be maintained along the LuaForge catalog. Unless this is a bad idea of course :-).
Someone else can fork the repository and you can say that their fork
is now the 'canonical' fork.. or the community will police itself.
That's the way most other projects are handled and while not perfect
it seems to work well enough. There is no real transfer of ownership,
although you can allow another user to commit to your fork of the
Creating a special 'Lua' user just isn't practical based on the limits
that Github imposes on users, and it goes against the whole 'social
networking' aspect of project development that they try to push.