[FM Discuss] questions about place

Aleksandar Erkalovic aerkalov at gmail.com
Mon Feb 8 12:30:49 PST 2010


ok.. i think this is very useful  discussion :)

when it comes to source repository and trac instalation it is not a
problem. booki.cc
and booki-dev are the same machine (fm.net is not). it is just matter
of dns and apache configuration.
it is very limited machine but we will change it in the future. it was
just "some" machine
for development.

basicly we first created booki.flossmanuals.net + booki-dev.flossmanuals.net and
then later adam noticed booki.cc is free domain. i never really
thought much about
this before  but it seems it is not clear to everyone what is "booki
service", "booki code"
and where to find them. so thanks to this discussion i can say there
will be some
changes in the future :)

when it comes to software there is more then just booki. there is: old
twiki code,
booki, objavi, espri... it is developed under the name flossmanuals
(also name of the
organisation). soooooo. i think it is perfectly ok if software stays
under flossmanuals.net domain. it will probably
be dev.flossmanuals.net (non functional link now) where we will put
info+download
for everything we produce. and from there we even might link to sites like
dev.flossmanuals.net/objavi/, dev.booki.cc, github, sourceforge or wherever
we  decide to host that specific software.

i guess identi.ca and statusnet works like that. identi.ca is a
service, statusnet is
name of the company and also name of the software. in our case booki is name
of the software and also name of the service but that could be changed
in the future
to help people better understand does "you can use booki for it" means "use
software and install it localy on your machine" or "use booki
service". right now
alternative name lives in the comedy land. it is BooKi :) but i am
perfectly ok to
have the same name for booki service and booki software but call all
other installations
something like "booki node". because in the future they are all
suppose to be connected
and share data.... but psssttttttt about that.

anyhoo, i think booki.cc and booki is something like mate (
http://en.wikipedia.org/wiki/Mate_%28beverage%29 ).
mate can be beverage but also mate can be gourd from which you drink mate :)

aco

On Mon, Feb 8, 2010 at 3:30 PM, Joshua Facemyer <jfacemyer at gmail.com> wrote:
> I'm really not intending to be contentious without reason, so I apologize if
> I come across that way.
>
> If booki is intended to be developed in an open-source model, I think it
> would behoove itself to be put in a place which is consistent (name-wise)
> for usability.  (If I'm looking for booki software, I wouldn't think to look
> on an FM domain).  I realize that Google et al. is probably how many people
> will find it, but I had just assumed that the same reasons for moving the
> collaboration part of FM to booki.cc would apply to the dev part of booki.
>
> If you don't agree, that's fine - it isn't that big of an issue for me :)  I
> don't want to make a big argument out of it (I hadn't realized until now
> that you were actually disagreeing, I thought you were just trying to
> clarify what I had meant).  I know it's a big hassle to move source repos,
> and in the end, I'm sure it will work fine no matter where it is.
>
> JF
>
> On 02/08/2010 08:46 AM, adam wrote:
>>
>> i am really sorry. i just dont get these questions. what importance is
>> it where booki is placed for dev? we have a tech set up. we have told
>> everyone where it is. why change it?
>>
>> adam
>>
>>
>>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.flossmanuals.net
> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
>



-- 
 http://www.binarni.net/



More information about the Discuss mailing list