Log message #901671

# At Username Text
# Jul 20th 2009, 15:49 ProLoser|Work vs what? make tickets?
# Jul 20th 2009, 15:49 markstory I like that people can only comment on things.
# Jul 20th 2009, 15:48 alkemann markstory: yea linking is ok, i do that for my projects. the "problem" with that is that it makes the article a one way communication. i want to see it become more of a community tool
# Jul 20th 2009, 15:47 ProLoser|Work meh i'm just trying to keep the code's development and the bakery as connected as possible
# Jul 20th 2009, 15:46 markstory well nothing lives forever.
# Jul 20th 2009, 15:46 ProLoser|Work like a new repo i mean
# Jul 20th 2009, 15:46 ProLoser|Work to the article
# Jul 20th 2009, 15:46 ProLoser|Work but you can still vote to relink the repo
# Jul 20th 2009, 15:46 ProLoser|Work ya, it's a problem when the master at that location goes awol
# Jul 20th 2009, 15:45 markstory a remote repo viewer assumes these repos provide that information.
# Jul 20th 2009, 15:45 ProLoser|Work lol
# Jul 20th 2009, 15:45 ProLoser|Work oh, maybe i misread ur punctuation
# Jul 20th 2009, 15:45 markstory I know, I can read.
# Jul 20th 2009, 15:45 ProLoser|Work it's only a viewer for remote repos
# Jul 20th 2009, 15:45 ProLoser|Work that's not /making/ repos
# Jul 20th 2009, 15:44 markstory I would think just linking to repos would be easier, than making repos like in ProLoser|Work's ticket.
# Jul 20th 2009, 15:44 ProLoser|Work !log
# Jul 20th 2009, 15:43 ProLoser|Work lame
# Jul 20th 2009, 15:43 ProLoser|Work ...
# Jul 20th 2009, 15:43 alkemann but yea, we should not make bakery into a thechaw / github clone. i dont know how to best solve this yet
# Jul 20th 2009, 15:42 ProLoser|Work seriously am i on mute? http://thechaw.com/bakery/tickets/view/4
# Jul 20th 2009, 15:41 alkemann well i guess that depends on how much of that backend we develop and how much we steal from thechaw :p
# Jul 20th 2009, 15:41 ProLoser|Work did you guys read my ticket about the repo viewer?
# Jul 20th 2009, 15:40 alkemann author is awol for a time, another person has been updating his fork, others have started requesting commits to this version. at some point it should become the new main code for the article
# Jul 20th 2009, 15:40 ADmad s/could/cause
# Jul 20th 2009, 15:40 ADmad agre.. but this would be after the intial release right.. could it would take quite some time to develop all that shit
# Jul 20th 2009, 15:40 ProLoser|Work wait do you mean a local repo
# Jul 20th 2009, 15:40 ProLoser|Work i thought you guys didn't like that
# Jul 20th 2009, 15:40 alkemann and create forks, branches, patches
# Jul 20th 2009, 15:39 ProLoser|Work ... i was talking about that
# Jul 20th 2009, 15:39 alkemann so people can update easily
# Jul 20th 2009, 15:39 alkemann i think we really need to have all shared code (not code exmaples) in a repo thing
# Jul 20th 2009, 15:39 ADmad i didnt know that part.. then it sounds good
# Jul 20th 2009, 15:38 ProLoser|Work you guys think there should be a master?
# Jul 20th 2009, 15:38 alkemann sure, but code commits would be against branches or forks, the master would merge into the master head
# Jul 20th 2009, 15:38 ADmad yeah that was my understanding too
# Jul 20th 2009, 15:38 alkemann we had some brainstorms in berlin about how to make it a more community tool and one of the ideas i like is that if an author dissapears or wants to give it up, there is a vote or the guy with the most accepted commits becomes the new master
# Jul 20th 2009, 15:37 ADmad alkemann: if you wikify cant anybody make updates ?
# Jul 20th 2009, 15:37 ProLoser|Work with moderation, is that a bad thing?
# Jul 20th 2009, 15:36 alkemann how so?
# Jul 20th 2009, 15:36 ADmad but on the downside you would lose control over your code..