Hi and welcome! On 12 April 2013 16:38, Shiva Teja <[email protected]> wrote: > Hello everyone. > > I am Shiva Teja, 2nd year CS undergrad, IIT Mandi, India. I'll be > participating in GSoC 2013. I came to know about Apache Bloodhound today > and I've decided to work on it. Interestingly, I liked almost all the > ideas. So I'm not sure about which one to choose now. I haven't installed > it/started experimenting on it yet(Sorry if you expected me to that before > mail, just couldn't resist enthusiasm). I'll be starting the work now. > These are my opinions/doubts on the ideas that I liked : > > 1. Ticket workflows enhancements : > Sounds interesting. Currently I'm not sure how to implement it. I guess I > can think about it once I understand Bloodhound's code base and APIs. About > the WYSIWYG editor, I came across two of these recently on Hacker news. > http://imperavi.com/redactor/ and > http://jhollingworth.github.io/bootstrap-wysihtml5/ . Can we use something > like these ?.
I see that the "WYSIWYG editor" term was badly chosen on my part. Sorry for that. What I ment was a visual graph editor for states and transitions in a workflow. It is an optional part of the task and you can use any JS library as long as: 1. It's license is compatible with ASF 2. It plays nice with Boostrap/JQuery 3. Is customizable enough to "fit nicely" into page layout 4. Is reasonably well supported (not dead for the last two years) ... or if you are a HTML5/JS enthusiast, you can build one from scratch as it was ment to be the "fun" part of the task. > > 2. Twitter card integration(and other social tags): > So just add meta tags dynamically ? Looks easy. Is it worth working on this > project for 2 months ? I think this should not take much time. Correct me > if I am wrong. > > 3. Expose TODOs from the code base in the UI : > Again, even this looks easy. As "rjollos" already commented on it something > similar has been done. https://trac-hacks.org/wiki/CodeTagsPlugin . > > 4. Patch workflows tightly coupled to version control: > This one has my attention. I might get to learn a lot from this project > compared to others. > > I still have doubts on few other projects. I will get back once I am in a > position to think about the implementation details(probably on irc). I > think I can finish any of these projects so I want to work on the project > that is most important to Bloodhound. If I choose an easy project, I will > provide UI enhancements to Bloodhound. I've used bootstrap before for my > personal stuff. > > > Regarding my experience, I consider myself as an intermediate python > programmer. Projects I've worked on are mostly based on python web > frameworks like tornado, flask and Google App Engine. > > > Are there any "must" do things like fixing a few bugs before I apply ? Or > can I just work on code samples for the project ? > > Any comments/suggestions ? > > Thanks in advance. > > Shiva Teja.
