[Outreachy] Git remote whitelist/blacklist

[Outreachy] Git remote whitelist/blacklist

[elena petrashen]

Hi,

I'm thinking of applying to Outreachy program this round with Git
and the project I'm really interested in is "Git remote whitelist/blacklist"
project (http://git.github.io/SoC-2016-Ideas/).
I have drafted the description/timeline for this project
and it would be great to get feedback/suggestions.
(I'm actually a bit confused about the scale of this. The
Outreachy application doesn't ask for "proposal" in the way
GSoC seems to, but merely requests "details and the timeline",
so I'm not sure whether the shorter description of what's planned
is expected or should I go deeper in detail. I apologize if I
chose a wrong approach.)

Thank you!

>> What project(s) are you interested in (these can be in the
same or different organizations)?
My preferred project to work on is Git remote whitelist/blacklist
project listed on http://git.github.io/SoC-2016-Ideas/. I'm really
interested in doing this project as I think this kind of effort is
really important: I recently started using git myself, and sometimes
I was really scared to push something to the location I was not
supposed to push to. I would really appreciate the opportunity in
participating in making git a bit more newbie-friendly.

>> Who is a possible mentor for the project you are most interested in?
Lars Schneider

>> Please describe the details and the timeline of the work you
plan to accomplish on the project you are most interested in (discuss
these first with the mentor of the project):
The goal is to provide a safer environment for newcomers to Git to
 enabling the possibility to modify git config, adding there "allowed"
 and "denied" remotes for pushing. Code, tests, and documentation
 are to be created.

Timeline:
0. Analysis
  Apr 22 - May 22 - studying the current code and drafting the
implementation proposal
1. Design
 a. May 22-June 1 - discussion with the mentor regarding the task,
presenting the approach and amending it per mentor's feedback
 b. June 1st-June 15th - communicating with the community
regarding the suggested changes and agreeing on logic, scope
and format of changes.
2. Development
 c. June 15th-July 1st - submitting code for the first basic version,
amending it according to the feedback
 d. July 1st - July 15th - extending the code to cover all of the
agreed scope
 e. July 15th - Aug 1st - finalizing full coverage with tests and
documentation
3. Evaluation
 f. Aug 1st - Aug 23rd - adding nice-to-have features and other
suggestion by the community

Re: [Outreachy] Git remote whitelist/blacklist

[elena petrashen]

Hi everyone,

I think I will submit the application as it is now, but still
it would be great to get feedback on it, as I don't think
there was no reply because everything was perfect :(

Thank you! And have an awesome weekend.

On Thu, Mar 24, 2016 at 5:50 PM, elena petrashen
<elena.petrashen@gmail.com> wrote:
> Hi,
>
> I'm thinking of applying to Outreachy program this round with Git
> and the project I'm really interested in is "Git remote whitelist/blacklist"
> project (http://git.github.io/SoC-2016-Ideas/).
> I have drafted the description/timeline for this project
> and it would be great to get feedback/suggestions.
> (I'm actually a bit confused about the scale of this. The
> Outreachy application doesn't ask for "proposal" in the way
> GSoC seems to, but merely requests "details and the timeline",
> so I'm not sure whether the shorter description of what's planned
> is expected or should I go deeper in detail. I apologize if I
> chose a wrong approach.)
>
> Thank you!
>
>>> What project(s) are you interested in (these can be in the
> same or different organizations)?
> My preferred project to work on is Git remote whitelist/blacklist
> project listed on http://git.github.io/SoC-2016-Ideas/. I'm really
> interested in doing this project as I think this kind of effort is
> really important: I recently started using git myself, and sometimes
> I was really scared to push something to the location I was not
> supposed to push to. I would really appreciate the opportunity in
> participating in making git a bit more newbie-friendly.
>
>>> Who is a possible mentor for the project you are most interested in?
> Lars Schneider
>
>>> Please describe the details and the timeline of the work you
> plan to accomplish on the project you are most interested in (discuss
> these first with the mentor of the project):
> The goal is to provide a safer environment for newcomers to Git to
>  enabling the possibility to modify git config, adding there "allowed"
>  and "denied" remotes for pushing. Code, tests, and documentation
>  are to be created.
>
> Timeline:
> 0. Analysis
>   Apr 22 - May 22 - studying the current code and drafting the
> implementation proposal
> 1. Design
>  a. May 22-June 1 - discussion with the mentor regarding the task,
> presenting the approach and amending it per mentor's feedback
>  b. June 1st-June 15th - communicating with the community
> regarding the suggested changes and agreeing on logic, scope
> and format of changes.
> 2. Development
>  c. June 15th-July 1st - submitting code for the first basic version,
> amending it according to the feedback
>  d. July 1st - July 15th - extending the code to cover all of the
> agreed scope
>  e. July 15th - Aug 1st - finalizing full coverage with tests and
> documentation
> 3. Evaluation
>  f. Aug 1st - Aug 23rd - adding nice-to-have features and other
> suggestion by the community

Re: [Outreachy] Git remote whitelist/blacklist

[Lars Schneider]

Hi Elena,

sorry for the late reply. I think it is great that you are interested in the Git remote whitelist/blacklist idea. Unfortunately I don't have any experience with Outreachy and I wonder what kind of feedback you are looking for.

Thanks,
Lars


> On 26 Mar 2016, at 13:15, elena petrashen <elena.petrashen@gmail.com> wrote:
> 
> Hi everyone,
> 
> I think I will submit the application as it is now, but still
> it would be great to get feedback on it, as I don't think
> there was no reply because everything was perfect :(
> 
> Thank you! And have an awesome weekend.
> 
> On Thu, Mar 24, 2016 at 5:50 PM, elena petrashen
> <elena.petrashen@gmail.com> wrote:
>> Hi,
>> 
>> I'm thinking of applying to Outreachy program this round with Git
>> and the project I'm really interested in is "Git remote whitelist/blacklist"
>> project (http://git.github.io/SoC-2016-Ideas/).
>> I have drafted the description/timeline for this project
>> and it would be great to get feedback/suggestions.
>> (I'm actually a bit confused about the scale of this. The
>> Outreachy application doesn't ask for "proposal" in the way
>> GSoC seems to, but merely requests "details and the timeline",
>> so I'm not sure whether the shorter description of what's planned
>> is expected or should I go deeper in detail. I apologize if I
>> chose a wrong approach.)
>> 
>> Thank you!
>> 
>>>> What project(s) are you interested in (these can be in the
>> same or different organizations)?
>> My preferred project to work on is Git remote whitelist/blacklist
>> project listed on http://git.github.io/SoC-2016-Ideas/. I'm really
>> interested in doing this project as I think this kind of effort is
>> really important: I recently started using git myself, and sometimes
>> I was really scared to push something to the location I was not
>> supposed to push to. I would really appreciate the opportunity in
>> participating in making git a bit more newbie-friendly.
>> 
>>>> Who is a possible mentor for the project you are most interested in?
>> Lars Schneider
>> 
>>>> Please describe the details and the timeline of the work you
>> plan to accomplish on the project you are most interested in (discuss
>> these first with the mentor of the project):
>> The goal is to provide a safer environment for newcomers to Git to
>> enabling the possibility to modify git config, adding there "allowed"
>> and "denied" remotes for pushing. Code, tests, and documentation
>> are to be created.
>> 
>> Timeline:
>> 0. Analysis
>>  Apr 22 - May 22 - studying the current code and drafting the
>> implementation proposal
>> 1. Design
>> a. May 22-June 1 - discussion with the mentor regarding the task,
>> presenting the approach and amending it per mentor's feedback
>> b. June 1st-June 15th - communicating with the community
>> regarding the suggested changes and agreeing on logic, scope
>> and format of changes.
>> 2. Development
>> c. June 15th-July 1st - submitting code for the first basic version,
>> amending it according to the feedback
>> d. July 1st - July 15th - extending the code to cover all of the
>> agreed scope
>> e. July 15th - Aug 1st - finalizing full coverage with tests and
>> documentation
>> 3. Evaluation
>> f. Aug 1st - Aug 23rd - adding nice-to-have features and other
>> suggestion by the community
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Outreachy] Git remote whitelist/blacklist

[Lars Schneider]

Hi Elena,

I thought a bit more about your proposal. The Outreachy internship is scheduled for 3 months and I think you would be able to come up with a "Git remote whitelist/blacklist" implementation that the Git list considers to accept within a month. In that case it would be good if you would have a few extra ideas in your Outreachy proposal that you could tackle afterwards. These extras could be extensions to the "whitelist/blacklist" project or a contribution to a completely different part of Git. According to the Outreachy page [1] you can still change your application until April 22.

In addition I wonder if you would be willing to start slowly with the "drafting the implementation" task even before April 22. I, and AFAIK the majority of the other people on the list, do not work full time on Git. That means some email responses might be delayed for reasons unrelated to Git. Therefore I think you will have a better experience if you work with a steady slow pace instead of high burst of list activity :-)

Cheers,
Lars
  

[1] https://wiki.gnome.org/Outreachy#Submit_an_Application


> On 29 Mar 2016, at 21:24, Lars Schneider <larsxschneider@gmail.com> wrote:
> 
> Hi Elena,
> 
> sorry for the late reply. I think it is great that you are interested in the Git remote whitelist/blacklist idea. Unfortunately I don't have any experience with Outreachy and I wonder what kind of feedback you are looking for.
> 
> Thanks,
> Lars
> 
> 
>> On 26 Mar 2016, at 13:15, elena petrashen <elena.petrashen@gmail.com> wrote:
>> 
>> Hi everyone,
>> 
>> I think I will submit the application as it is now, but still
>> it would be great to get feedback on it, as I don't think
>> there was no reply because everything was perfect :(
>> 
>> Thank you! And have an awesome weekend.
>> 
>> On Thu, Mar 24, 2016 at 5:50 PM, elena petrashen
>> <elena.petrashen@gmail.com> wrote:
>>> Hi,
>>> 
>>> I'm thinking of applying to Outreachy program this round with Git
>>> and the project I'm really interested in is "Git remote whitelist/blacklist"
>>> project (http://git.github.io/SoC-2016-Ideas/).
>>> I have drafted the description/timeline for this project
>>> and it would be great to get feedback/suggestions.
>>> (I'm actually a bit confused about the scale of this. The
>>> Outreachy application doesn't ask for "proposal" in the way
>>> GSoC seems to, but merely requests "details and the timeline",
>>> so I'm not sure whether the shorter description of what's planned
>>> is expected or should I go deeper in detail. I apologize if I
>>> chose a wrong approach.)
>>> 
>>> Thank you!
>>> 
>>>>> What project(s) are you interested in (these can be in the
>>> same or different organizations)?
>>> My preferred project to work on is Git remote whitelist/blacklist
>>> project listed on http://git.github.io/SoC-2016-Ideas/. I'm really
>>> interested in doing this project as I think this kind of effort is
>>> really important: I recently started using git myself, and sometimes
>>> I was really scared to push something to the location I was not
>>> supposed to push to. I would really appreciate the opportunity in
>>> participating in making git a bit more newbie-friendly.
>>> 
>>>>> Who is a possible mentor for the project you are most interested in?
>>> Lars Schneider
>>> 
>>>>> Please describe the details and the timeline of the work you
>>> plan to accomplish on the project you are most interested in (discuss
>>> these first with the mentor of the project):
>>> The goal is to provide a safer environment for newcomers to Git to
>>> enabling the possibility to modify git config, adding there "allowed"
>>> and "denied" remotes for pushing. Code, tests, and documentation
>>> are to be created.
>>> 
>>> Timeline:
>>> 0. Analysis
>>> Apr 22 - May 22 - studying the current code and drafting the
>>> implementation proposal
>>> 1. Design
>>> a. May 22-June 1 - discussion with the mentor regarding the task,
>>> presenting the approach and amending it per mentor's feedback
>>> b. June 1st-June 15th - communicating with the community
>>> regarding the suggested changes and agreeing on logic, scope
>>> and format of changes.
>>> 2. Development
>>> c. June 15th-July 1st - submitting code for the first basic version,
>>> amending it according to the feedback
>>> d. July 1st - July 15th - extending the code to cover all of the
>>> agreed scope
>>> e. July 15th - Aug 1st - finalizing full coverage with tests and
>>> documentation
>>> 3. Evaluation
>>> f. Aug 1st - Aug 23rd - adding nice-to-have features and other
>>> suggestion by the community
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: [Outreachy] Git remote whitelist/blacklist

[elena petrashen]

Hi Lars,

thank you so much for reaching out to me! and thank you for your
suggestions too, I'm changing my application to reflect those. It does
really make sense to start the discussion earlier then I scheduled,
and add some extra ideas that could be completed after the
whitelist/blacklist. Probably if those ideas are the extensions to the
whitelist/blacklist, they could be also agreed on when discussing the
overall project scope.

Cheers,
Elena

On Wed, Mar 30, 2016 at 11:21 AM, Lars Schneider
<larsxschneider@gmail.com> wrote:
> Hi Elena,
>
> I thought a bit more about your proposal. The Outreachy internship is scheduled for 3 months and I think you would be able to come up with a "Git remote whitelist/blacklist" implementation that the Git list considers to accept within a month. In that case it would be good if you would have a few extra ideas in your Outreachy proposal that you could tackle afterwards. These extras could be extensions to the "whitelist/blacklist" project or a contribution to a completely different part of Git. According to the Outreachy page [1] you can still change your application until April 22.
>
> In addition I wonder if you would be willing to start slowly with the "drafting the implementation" task even before April 22. I, and AFAIK the majority of the other people on the list, do not work full time on Git. That means some email responses might be delayed for reasons unrelated to Git. Therefore I think you will have a better experience if you work with a steady slow pace instead of high burst of list activity :-)
>
> Cheers,
> Lars
>
>
> [1] https://wiki.gnome.org/Outreachy#Submit_an_Application
>
>
>> On 29 Mar 2016, at 21:24, Lars Schneider <larsxschneider@gmail.com> wrote:
>>
>> Hi Elena,
>>
>> sorry for the late reply. I think it is great that you are interested in the Git remote whitelist/blacklist idea. Unfortunately I don't have any experience with Outreachy and I wonder what kind of feedback you are looking for.
>>
>> Thanks,
>> Lars
>>
>>
>>> On 26 Mar 2016, at 13:15, elena petrashen <elena.petrashen@gmail.com> wrote:
>>>
>>> Hi everyone,
>>>
>>> I think I will submit the application as it is now, but still
>>> it would be great to get feedback on it, as I don't think
>>> there was no reply because everything was perfect :(
>>>
>>> Thank you! And have an awesome weekend.
>>>
>>> On Thu, Mar 24, 2016 at 5:50 PM, elena petrashen
>>> <elena.petrashen@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> I'm thinking of applying to Outreachy program this round with Git
>>>> and the project I'm really interested in is "Git remote whitelist/blacklist"
>>>> project (http://git.github.io/SoC-2016-Ideas/).
>>>> I have drafted the description/timeline for this project
>>>> and it would be great to get feedback/suggestions.
>>>> (I'm actually a bit confused about the scale of this. The
>>>> Outreachy application doesn't ask for "proposal" in the way
>>>> GSoC seems to, but merely requests "details and the timeline",
>>>> so I'm not sure whether the shorter description of what's planned
>>>> is expected or should I go deeper in detail. I apologize if I
>>>> chose a wrong approach.)
>>>>
>>>> Thank you!
>>>>
>>>>>> What project(s) are you interested in (these can be in the
>>>> same or different organizations)?
>>>> My preferred project to work on is Git remote whitelist/blacklist
>>>> project listed on http://git.github.io/SoC-2016-Ideas/. I'm really
>>>> interested in doing this project as I think this kind of effort is
>>>> really important: I recently started using git myself, and sometimes
>>>> I was really scared to push something to the location I was not
>>>> supposed to push to. I would really appreciate the opportunity in
>>>> participating in making git a bit more newbie-friendly.
>>>>
>>>>>> Who is a possible mentor for the project you are most interested in?
>>>> Lars Schneider
>>>>
>>>>>> Please describe the details and the timeline of the work you
>>>> plan to accomplish on the project you are most interested in (discuss
>>>> these first with the mentor of the project):
>>>> The goal is to provide a safer environment for newcomers to Git to
>>>> enabling the possibility to modify git config, adding there "allowed"
>>>> and "denied" remotes for pushing. Code, tests, and documentation
>>>> are to be created.
>>>>
>>>> Timeline:
>>>> 0. Analysis
>>>> Apr 22 - May 22 - studying the current code and drafting the
>>>> implementation proposal
>>>> 1. Design
>>>> a. May 22-June 1 - discussion with the mentor regarding the task,
>>>> presenting the approach and amending it per mentor's feedback
>>>> b. June 1st-June 15th - communicating with the community
>>>> regarding the suggested changes and agreeing on logic, scope
>>>> and format of changes.
>>>> 2. Development
>>>> c. June 15th-July 1st - submitting code for the first basic version,
>>>> amending it according to the feedback
>>>> d. July 1st - July 15th - extending the code to cover all of the
>>>> agreed scope
>>>> e. July 15th - Aug 1st - finalizing full coverage with tests and
>>>> documentation
>>>> 3. Evaluation
>>>> f. Aug 1st - Aug 23rd - adding nice-to-have features and other
>>>> suggestion by the community
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe git" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>

Re: [Outreachy] Git remote whitelist/blacklist

[Lars Schneider]

Hi Elena,

I think you application could really stand out if you describe how 
you intend to approach the remote whitelist/blacklist task in a bit more
detail. What files/functions do you intend to modify? Can you reuse existing 
functions? What new functions do you plan to add? How do you intend to test the
feature? Could you imagine a (command line) user interface for the feature 
beyond the suggested git config?

You could also post a very rough RFC (request for comment) patch to show
how you would implement a part of the task.

Cheers,
Lars


On 04 Apr 2016, at 22:21, elena petrashen <elena.petrashen@gmail.com> wrote:

> Hi Lars,
> 
> thank you so much for reaching out to me! and thank you for your
> suggestions too, I'm changing my application to reflect those. It does
> really make sense to start the discussion earlier then I scheduled,
> and add some extra ideas that could be completed after the
> whitelist/blacklist. Probably if those ideas are the extensions to the
> whitelist/blacklist, they could be also agreed on when discussing the
> overall project scope.
> 
> Cheers,
> Elena
> 
> On Wed, Mar 30, 2016 at 11:21 AM, Lars Schneider
> <larsxschneider@gmail.com> wrote:
>> Hi Elena,
>> 
>> I thought a bit more about your proposal. The Outreachy internship is scheduled for 3 months and I think you would be able to come up with a "Git remote whitelist/blacklist" implementation that the Git list considers to accept within a month. In that case it would be good if you would have a few extra ideas in your Outreachy proposal that you could tackle afterwards. These extras could be extensions to the "whitelist/blacklist" project or a contribution to a completely different part of Git. According to the Outreachy page [1] you can still change your application until April 22.
>> 
>> In addition I wonder if you would be willing to start slowly with the "drafting the implementation" task even before April 22. I, and AFAIK the majority of the other people on the list, do not work full time on Git. That means some email responses might be delayed for reasons unrelated to Git. Therefore I think you will have a better experience if you work with a steady slow pace instead of high burst of list activity :-)
>> 
>> Cheers,
>> Lars
>> 
>> 
>> [1] https://wiki.gnome.org/Outreachy#Submit_an_Application
>> 
>> 
>>> On 29 Mar 2016, at 21:24, Lars Schneider <larsxschneider@gmail.com> wrote:
>>> 
>>> Hi Elena,
>>> 
>>> sorry for the late reply. I think it is great that you are interested in the Git remote whitelist/blacklist idea. Unfortunately I don't have any experience with Outreachy and I wonder what kind of feedback you are looking for.
>>> 
>>> Thanks,
>>> Lars
>>> 
>>> 
>>>> On 26 Mar 2016, at 13:15, elena petrashen <elena.petrashen@gmail.com> wrote:
>>>> 
>>>> Hi everyone,
>>>> 
>>>> I think I will submit the application as it is now, but still
>>>> it would be great to get feedback on it, as I don't think
>>>> there was no reply because everything was perfect :(
>>>> 
>>>> Thank you! And have an awesome weekend.
>>>> 
>>>> On Thu, Mar 24, 2016 at 5:50 PM, elena petrashen
>>>> <elena.petrashen@gmail.com> wrote:
>>>>> Hi,
>>>>> 
>>>>> I'm thinking of applying to Outreachy program this round with Git
>>>>> and the project I'm really interested in is "Git remote whitelist/blacklist"
>>>>> project (http://git.github.io/SoC-2016-Ideas/).
>>>>> I have drafted the description/timeline for this project
>>>>> and it would be great to get feedback/suggestions.
>>>>> (I'm actually a bit confused about the scale of this. The
>>>>> Outreachy application doesn't ask for "proposal" in the way
>>>>> GSoC seems to, but merely requests "details and the timeline",
>>>>> so I'm not sure whether the shorter description of what's planned
>>>>> is expected or should I go deeper in detail. I apologize if I
>>>>> chose a wrong approach.)
>>>>> 
>>>>> Thank you!
>>>>> 
>>>>>>> What project(s) are you interested in (these can be in the
>>>>> same or different organizations)?
>>>>> My preferred project to work on is Git remote whitelist/blacklist
>>>>> project listed on http://git.github.io/SoC-2016-Ideas/. I'm really
>>>>> interested in doing this project as I think this kind of effort is
>>>>> really important: I recently started using git myself, and sometimes
>>>>> I was really scared to push something to the location I was not
>>>>> supposed to push to. I would really appreciate the opportunity in
>>>>> participating in making git a bit more newbie-friendly.
>>>>> 
>>>>>>> Who is a possible mentor for the project you are most interested in?
>>>>> Lars Schneider
>>>>> 
>>>>>>> Please describe the details and the timeline of the work you
>>>>> plan to accomplish on the project you are most interested in (discuss
>>>>> these first with the mentor of the project):
>>>>> The goal is to provide a safer environment for newcomers to Git to
>>>>> enabling the possibility to modify git config, adding there "allowed"
>>>>> and "denied" remotes for pushing. Code, tests, and documentation
>>>>> are to be created.
>>>>> 
>>>>> Timeline:
>>>>> 0. Analysis
>>>>> Apr 22 - May 22 - studying the current code and drafting the
>>>>> implementation proposal
>>>>> 1. Design
>>>>> a. May 22-June 1 - discussion with the mentor regarding the task,
>>>>> presenting the approach and amending it per mentor's feedback
>>>>> b. June 1st-June 15th - communicating with the community
>>>>> regarding the suggested changes and agreeing on logic, scope
>>>>> and format of changes.
>>>>> 2. Development
>>>>> c. June 15th-July 1st - submitting code for the first basic version,
>>>>> amending it according to the feedback
>>>>> d. July 1st - July 15th - extending the code to cover all of the
>>>>> agreed scope
>>>>> e. July 15th - Aug 1st - finalizing full coverage with tests and
>>>>> documentation
>>>>> 3. Evaluation
>>>>> f. Aug 1st - Aug 23rd - adding nice-to-have features and other
>>>>> suggestion by the community
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe git" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> 
>> 
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Outreachy] Git remote whitelist/blacklist

[Matthieu Moy]

Lars Schneider <larsxschneider@gmail.com> writes:

> Hi Elena,
>
> I think you application could really stand out if you describe how 
> you intend to approach the remote whitelist/blacklist task in a bit more
> detail.

A few other hints on getting a good application:

What is expected here is a _convincing_ application, ie. have enough
arguments to convince the future mentor and the administrator of the
organization that if the project is accepted, then it will be a success.
Don't write your application as "I'd like to do this", but more as
"Here are proofs that if my application is accepted, then the project
will go smoothly".

There are two important points:

* Technical skills: a typical application shows that the applicant
  already looked at the code, understands the ins and outs: what code
  needs to be changed, how will it be tested, ...

* Interaction with the community: we like to discuss and iterate over
  our contributions. You (Elena) already saw this kind of discussion
  happen for your microproject, but we expect similar discussions for
  applications. For examples of such discussions, see:

    http://thread.gmane.org/gmane.comp.version-control.git/289700/focus=289869
    http://thread.gmane.org/gmane.comp.version-control.git/289299/focus=289407
    ...
    (this one is for GSoC, but it's very similar to Outreachy)

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/