Log message #901704

# At Username Text
# Jul 20th 2009, 15:54 alkemann like merge all twitter datasources into one "article" if they cant agree on somethng, have em branch their disagreements
# Jul 20th 2009, 15:53 alkemann but that isnt really the point. i would expect the vast majority of users to not use this feature. the point is to give a tool to the active members
# Jul 20th 2009, 15:52 alkemann assuming? no. trying to force them to start? yes!
# Jul 20th 2009, 15:52 markstory tar files don't exist because everyone knows how to use version control.
# Jul 20th 2009, 15:52 ADmad exactly
# Jul 20th 2009, 15:52 markstory alkemann: you're assuming people know how to use version control.
# Jul 20th 2009, 15:52 alkemann markstory: if people could make their own branches, it would be just cherrypicking
# Jul 20th 2009, 15:52 ProLoser|Work and then you have multiple people heavily working on each module
# Jul 20th 2009, 15:52 ProLoser|Work for each module
# Jul 20th 2009, 15:51 ProLoser|Work yes but it becomes a drupal-centric community that can submit patches, add tickets, update the wiki
# Jul 20th 2009, 15:51 markstory which necessitates diff files
# Jul 20th 2009, 15:51 markstory and drupal still requires the owner to commit things.
# Jul 20th 2009, 15:51 markstory ProLoser|Work: well I'm just basing things off of my experience.
# Jul 20th 2009, 15:50 alkemann markstory: anyway we got here, this is where we are :)
# Jul 20th 2009, 15:50 ProLoser|Work one of the reasons why drupal is so successfull is the module development teams
# Jul 20th 2009, 15:50 ProLoser|Work ... oh come on now
# Jul 20th 2009, 15:50 markstory alkemann: only because people don't know how to generate diffs.
# Jul 20th 2009, 15:49 alkemann but having to recreate history by reading the entire comment thread : add this, remove this . change that.. it's just not userfriendly
# Jul 20th 2009, 15:49 markstory I think with all the code I've published outside of debug kit, I've gotten less than 10 patches. ever.
# 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