| # |
Apr 26th 2010, 01:47 |
real34 |
as soon as we'll know what is needed, implementing it will be fast and we could have more people involved with it |
| # |
Apr 26th 2010, 01:47 |
real34 |
I'll try to set the bakery up in local and dig in the numerous branches to see what could I could do to help, but imo what is most needed atm are just specifications! |
| # |
Apr 26th 2010, 01:45 |
savant |
I should redump the db to be honest as the schema has changed and I haven't been diligent on making migrations, but there are only two developers working on it (myself and ProLoser) so it hasn't been a big deal |
| # |
Apr 26th 2010, 01:45 |
savant |
most of the github specific code is in a single model and it's controller |
| # |
Apr 26th 2010, 01:43 |
savant |
that hits github directly, but assuming I added codaset support, that would just mean making a switch or a helper to handle it |
| # |
Apr 26th 2010, 01:43 |
real34 |
ok |
| # |
Apr 26th 2010, 01:42 |
savant |
about the only thing github specific that would need refactoring is the news feed on each user/repository |
| # |
Apr 26th 2010, 01:42 |
savant |
i've been toying locally with hitting redmine for stuff |
| # |
Apr 26th 2010, 01:41 |
savant |
real34: not really. i have plans to allow it to access codaset once joel moss releases an api for it |
| # |
Apr 26th 2010, 01:41 |
savant |
i thought about making the account I have on github (cakephp-plugin-server) make pull requests to all developers on github with non-compliant cakephp app or plugin code |
| # |
Apr 26th 2010, 01:41 |
real34 |
savant, is there anything specific to github or could it be easily extended to any git repo? |
| # |
Apr 26th 2010, 01:40 |
savant |
next step is to serve them all up using git-svn and git-web |
| # |
Apr 26th 2010, 01:39 |
savant |
so now i have mirrors of every package I am indexing (about 577, give or take 10 that have been renamed or deleted) |
| # |
Apr 26th 2010, 01:39 |
savant |
i've squashed a few bugs recently |
| # |
Apr 26th 2010, 01:39 |
savant |
linking to a repo is easy |
| # |
Apr 26th 2010, 01:39 |
savant |
gisting is easy |
| # |
Apr 26th 2010, 01:38 |
savant |
probably |
| # |
Apr 26th 2010, 01:38 |
real34 |
do you think the code you did for cakepackages could be easily reused for the github interaction (to link a code to a repository or a gist)? |
| # |
Apr 26th 2010, 01:37 |
savant |
to be honest I'm about to just throw out all of the existing bakery code and rewrite from scratch |
| # |
Apr 26th 2010, 01:36 |
real34 |
I'm just like you! |
| # |
Apr 26th 2010, 01:35 |
savant |
well, im more than happy to help with whatever is needed |
| # |
Apr 26th 2010, 01:35 |
savant |
hmmm |
| # |
Apr 26th 2010, 01:34 |
real34 |
not yet... still a matter of time afaik :) |
| # |
Apr 26th 2010, 01:34 |
savant |
is that code open source yet? |
| # |
Apr 26th 2010, 01:34 |
real34 |
cakeqs was build with the idea of being multilingual and openid enabled, but it is just the beginning of a unique login |
| # |
Apr 26th 2010, 01:33 |
savant |
too many tools to be managed, and its too bad no one really has time to be dedicated to them, otherwise it would be kick ass |
| # |
Apr 26th 2010, 01:33 |
real34 |
I totally agree with that ;) and I think the CakePHP team and the CSF are aware of it. Imo it is just a matter of time for updating everything |
| # |
Apr 26th 2010, 01:32 |
savant |
oh and we can't forget live.cakephp.org, although it is usually forgotten for a few months |
| # |
Apr 26th 2010, 01:31 |
savant |
and then there is cakeforge, which is still hosting random things and being linked to by members (there is some good stuff there but it's getting sort of outdated) |
| # |
Apr 26th 2010, 01:31 |
savant |
and cakeqs should really replace the google groups, but you'd need to import the archive (does cakeqs integrate with the other logins?) |
| # |
Apr 26th 2010, 01:30 |
savant |
then there are the google groups, which get a modest amount of traffic, but usually the same questions |
| # |
Apr 26th 2010, 01:30 |
savant |
lighthouseapp is nice, but it requires yet another account on yet another service |
| # |
Apr 26th 2010, 01:29 |
savant |
the book is well built, but needs some work to make it apparent to all users that it is a wiki and they CAN contribute |
| # |
Apr 26th 2010, 01:29 |
savant |
the bakery is a smelly turd because people post their articles and the code isn't in a repository (git, svn or otherwise) |
| # |
Apr 26th 2010, 01:28 |
savant |
you have bin, which is awesome, but not tied to my user account |
| # |
Apr 26th 2010, 01:28 |
savant |
to be blunt, there are way too many disparate tools in use for the cakephp community |
| # |
Apr 26th 2010, 01:28 |
real34 |
that "non tech" decision-makers could read to see how Cake is awesome :) |
| # |
Apr 26th 2010, 01:27 |
real34 |
with all official announcements and community highlights |
| # |
Apr 26th 2010, 01:27 |
real34 |
a blog on news.cakephp.org for instance |
| # |
Apr 26th 2010, 01:27 |
real34 |
I initially thought about a simple setup of Croogo for another blog (simple / efficient), but the idea of having yet another tool is not optimal |
| # |
Apr 26th 2010, 01:26 |
savant |
communication? |