Hi Anze, It seems the proposal https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011 is unavailable. Again I don't know whether I need to submit a BEP or in other format to the mentoring programme. So I thought of making BEP first.
Regards, On Wed, Jul 10, 2013 at 12:30 PM, Anze Staric <[email protected]> wrote: > As far as I understand the description, live syntax highlighting is > performed while you are still editing content, so it should be done in > javascript (with some help of the server side when needed, but without > submitting the wiki). > > A good place to start writing your proposal is: > https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011 > > When logged in, you should be able to create the page. > > > Anze > > On Wed, Jul 10, 2013 at 7:02 AM, Anoop Nayak <[email protected]> > wrote: > > Hi all, > > > > First of all a big Thank you to all for considering me :). Regarding the > > JIRA issue #481 <https://issues.apache.org/bloodhound/ticket/481>, I > don't > > whether this is a stupid question. Since we need live syntax highlighting > > it should mostly be in Javascript right? And only the end result need to > be > > sent to server. I'm in process of creating a proposal for the ICFOSS > Apache > > Mentoring Programme by Luciano Resende. In the meanwhile can anybody > > suggest a place online where I can share my finished proposals so that > you > > all can review it? Hoping for a reply soon. > > > > @Pranay I would require your help in making proposals :). > > > > Regards, > > > > > > On Wed, Jul 10, 2013 at 12:29 AM, Pranay B. Sodre > > <[email protected]>wrote: > > > >> Hello Anoop- I am currently with the GSoC program. I am more than happy > to > >> share my knowledge. I am slightly delayed with my mail due to lack of > >> internet in my apartment, but I will get back to you as soon as I am > able > >> to with a response. There are also other GSoC participants. > >> > >> Pranay B. > >> > >> > >> > >> > >> On 9 July 2013 17:36, Gary Martin <[email protected]> wrote: > >> > >> > I expect it will end up being something fairly similar to the GSoC > scheme > >> > and so I don't think that we are meant to teach students how to > develop > >> in > >> > python so that shouldn't rule Joe out from being a mentor. > >> > > >> > I hope that Anoop will be able to submit a proposal on this basis. I > >> > expect that it would be advantageous to Anoop to share aspects of the > >> > proposal with the Bloodhound community in advance of the proposal > >> > submission deadline. This may give a chance for Anoop to improve the > >> > quality of the proposal. > >> > > >> > Anyway, I do hope we can get Anoop involved! I would also volunteer > if I > >> > thought that I could dedicate an appropriate amount of time but I will > >> > certainly try to help out whenever I can. > >> > > >> > Cheers, > >> > Gary > >> > > >> > > >> > On 08/07/13 18:47, Joachim Dreimann wrote: > >> > > >> >> Hi Anoop, > >> >> > >> >> I may be able to volunteer as a mentor, but I can only help with > >> >> community, > >> >> design and general questions: my python skills are very limited. > >> >> > >> >> Let me know if you'd still find that helpful. I do mentor current > Google > >> >> Summer of Code students, but that mainly works because other devs are > >> >> happy > >> >> to chip in with technical questions, answers and reviews. I assume > the > >> >> community will be happy to do so in future too. > >> >> > >> >> What are the exact dates again for the mentoring program? > >> >> Have you installed Bloodhound and tried to solve a starter ticket or > >> >> similar to become more familiar with it? > >> >> https://issues.apache.org/**bloodhound/wiki/**BloodhoundContributing > < > >> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing> > >> >> > >> >> Cheers, > >> >> Joe > >> >> > >> >> > >> >> > >> >> > >> >> On 3 July 2013 03:42, Anoop Nayak <[email protected]> wrote: > >> >> > >> >> Hi Brane, > >> >>> > >> >>> I looked through the BEP in detail. So should I make a BEP of the > issue > >> >>> 481. What would you suggest. And since I'm applying for the > mentoring > >> >>> program, it seems I need to find a mentor first and submit my > proposal > >> by > >> >>> July 15. In the meanwhile I'm digging deeper into code now. Please > do > >> >>> advice on what to do. > >> >>> > >> >>> And to all devs, since Brane is a little busy, would any of the > other > >> >>> devs > >> >>> able to help me out? > >> >>> > >> >>> Thanks in advance, > >> >>> Anoop > >> >>> > >> >>> On 30.06.2013 13:31, Anoop Nayak wrote: > >> >>> > >> >>>> Hi devs, > >> >>>> > >> >>>> I'm a newbie to open source and I knew about contributing to > >> opensource > >> >>>> projects only a week back. I had attended the ICFOSS ASF Mentoring > >> >>>> > >> >>> Program > >> >>> > >> >>>> from June 20th to 23rd conducted by Luciano Resende. I'm fairly > good > >> at > >> >>>> python and I currently am a student who earns a little doing Django > >> >>>> > >> >>> sites. > >> >>> > >> >>>> Since I'm totally new to the community I would like to get a mentor > >> for > >> >>>> > >> >>> the > >> >>> > >> >>>> project. For the past week I was learning on how Bloodhound works. > Now > >> >>>> > >> >>> that > >> >>> > >> >>>> I know a bit I think I'm ready to start off. Hoping for a positive > >> reply > >> >>>> soon. > >> >>>> > >> >>> Hi Anoop, > >> >>> > >> >>> Welcome! > >> >>> > >> >>> You really want to look at: > >> >>> > >> >>> https://issues.apache.org/**bloodhound/ticket/481< > >> https://issues.apache.org/bloodhound/ticket/481> > >> >>> > >> >>> Bloodhound is self-hosting and we only posted issues to Jira because > >> >>> that's where they get picked up from for GSoC submissions. :) > >> >>> > >> >>> Anyone on this list will be happy to help you along. The usual > approach > >> >>> is to begin a design discussion here on this list, and when the > >> >>> specifics of the feature you want to work on are a bit clearer, > follow > >> >>> that up with a formal feature proposal, see > >> >>> > >> >>> https://issues.apache.org/**bloodhound/wiki/Proposals< > >> https://issues.apache.org/bloodhound/wiki/Proposals> > >> >>> > >> >>> Of course, none of the above red-tape is stopping you from just > diving > >> >>> in and hacking along, but we do prefer to have a BEP written up > fairly > >> >>> early -- it doubles as documentation as well as feature > specification. > >> >>> Regarding code changes, Please begin by reading the following: > >> >>> > >> >>> https://issues.apache.org/**bloodhound/wiki/** > >> >>> BloodhoundContributing< > >> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing> > >> >>> > >> >>> if you're not already an Apache committer (and I assume you're not; > I > >> >>> don't find your name on the list), you'll begin by submitting > patches > >> to > >> >>> this list, and someone will review them and commit them, giving > >> >>> appropriate credit. When we feel comfortable with your submissions, > >> >>> you'll be invited to become a committer and given commit access. > >> >>> > >> >>> Before that can happen, however, you'll have to submit an ICLA to > the > >> >>> ASF; see the section "Contributor License Agreements" here: > >> >>> > >> >>> http://www.apache.org/**licenses/ < > >> http://www.apache.org/licenses/> > >> >>> > >> >>> In fact I suggest you read that and perhaps submit the ICLA sooner > >> >>> rather than later. The ASF requires an ICLA for any non-trivial > >> >>> contributions. Also, if you don't feel comfortable with submitting > the > >> >>> ICLA, or your employer/schhool/etc. do not allow you to do so, it's > >> >>> better to be aware of that sooner rather than later. > >> >>> > >> >>> Do note that the ICLA is /not/ a copyright assignment: your work > >> remains > >> >>> your own. It is a license given by you to the ASF that it may > publish > >> >>> your contribution as part of an Apache release, licensed under the > >> >>> Apache License. Also, the ICLA is not binding in any way, it does > not > >> >>> require you to contribute code to the ASF, and any code that you do > not > >> >>> specifically contribute (i.e., post here as a patch proposal or > commit > >> >>> to the ASF repository) does not fall under its provisions. > >> >>> > >> >>> Finally -- I'd volunteer to be your mentor but right now don't have > >> >>> enough time to do that properly. If you have any questions about the > >> >>> project or the workings of the ASF, feel free to raise them on this > >> list. > >> >>> > >> >>> -- Brane > >> >>> > >> >>> -- > >> >>> Branko Čibej | Director of Subversion > >> >>> WANdisco // Non-Stop Data > >> >>> e. [email protected] > >> >>> > >> >>> > >> >> > >> >> > >> > > >> > > > > > > > > -- > > Anoop > -- Anoop
