Re: Confirming mentor status for GSoC and/or Outreachy

[Pranav Jain]

Dear Mentors,
I am waiting for mentors/co-mentor of following projects to reply to
"Confirming mentor status" mail.

   - Automatic builds of clang using OBS
   - EasyGnuPG Improvements
   - Install FreedomBox in a Container
   - OwnMailbox Improvements
   - Recognize Debian-Med contributions via ORCID
   - Virtual LTSP Server

If you are one of the mentor or co-mentor of these project then please
reply confirming your status. We are going to have a mentors meeting soon.
If in case you did send the mail then please resend it. We might have
missed it, sorry.

We have previously moved some projects to "Projects ideas without confirmed
mentors" [1] [2] list and would sadly have to do with others too.

[1] : https://wiki.debian.org/SummerOfCode2018/Projects#Projects
_ideas_without_confirmed_mentors
[2] : https://lists.debian.org/debian-outreach/2018/03/msg00070.html

On Thu, Mar 15, 2018 at 12:07 AM, Molly de Blanc  wrote:

> Dear Mentors,
>
> Greeting from Debian Outreach Team :)
>
> We are so thrilled to have you all as a part of Google Summer of Code
> 2018and/or Outreachywith Debian.
>
> The student application period has already started and we are doing a
> final role call to make sure that all mentors and co-mentors are still
> available for their projects.We're asking all mentors to reconfirm by
> responding to this email.
>
> Additionally, we're looking to plan an IRC meeting to check in with
> everyone, using the channel #debian-soc-mentors (pw: dpldance). Please
> share your time zone and any times that work well for you. We understand
> it will be hard to find a time that works for everyone.
>
> In your email, please include:
>
> 1. Your name
> 2. Project name
> 3. Are  you participating in GSoC or Outreachy with more than one
> organization?
> 4. Your time zone and times that work well for you.
>
> Please send the reply by 15th March. On March 16th, we'll remove
> projects without confirmed mentors.
>
> We will get back to you soon!
>
> Cheers,
>
> Your friendly Debian Outreach Team
>
>


-- 
Regards,

Pranav Jain

Re: tips for writing your proposal - more details (tools)

[Daniel Pocock]

On 13/03/18 20:12, Daniel Pocock wrote:

> 
> - tools you want to use:
>   - communication (names of IRC channels, email lists, other tools?)
>   - project management (will you use Kanboard or something else?)
>   - your IDE, e.g. Eclipse
>   - your desktop environment / Linux of choice
> 

I've started looking at student proposals, I'll send some individual
replies but also some general tips for everybody.

Please remember that in Debian, we are keen to avoid proprietary
services that hide their source code when there is a free alternative
available.

Here are some example:

Instead of Hangouts, some mentors prefer to use Jitsi Meet or rtc.debian.org

Instead of Github, some projects use salsa.debian.org

Instead of Slack, Debian uses IRC

Instead of Trello, some people use Kanboard


Why not visit https://meet.jit.si and try to make a call with a friend,
another student or even one of the mentors?  The Jisti Meet software is
all free software.

If your project proposal includes any specific tools, why not ask about
them on IRC?

I started a page about this here:

https://wiki.debian.org/Teams/Outreach/Tools

and mentors and students are welcome to contribute.

If you want to use Kanaboard, which instance will you use and how will
you get an account to log in?  Please share your ideas about it.

Re: Confirming mentor status for GSoC and/or Outreachy

[Dashamir Hoxha]

On Mon, Mar 19, 2018 at 9:14 AM, Pranav Jain  wrote:

> Dear Mentors,
> I am waiting for mentors/co-mentor of following projects to reply to
> "Confirming mentor status" mail.
>
>- Automatic builds of clang using OBS
>- EasyGnuPG Improvements
>- Install FreedomBox in a Container
>- OwnMailbox Improvements
>- Recognize Debian-Med contributions via ORCID
>- Virtual LTSP Server
>
> If you are one of the mentor or co-mentor of these project then please
> reply confirming your status. We are going to have a mentors meeting soon.
> If in case you did send the mail then please resend it. We might have
> missed it, sorry.
>
> We have previously moved some projects to "Projects ideas without
> confirmed mentors" [1] [2] list and would sadly have to do with others too.
>
> [1] : https://wiki.debian.org/SummerOfCode2018/Projects#Projects
> _ideas_without_confirmed_mentors
> [2] : https://lists.debian.org/debian-outreach/2018/03/msg00070.html
>

Yes of course you have missed it.
It is easy to miss things when you communicate in plain email.

-- Forwarded message --
From: Dashamir Hoxha 
Date: Thu, Mar 15, 2018 at 4:56 PM
Subject: Re: Confirming mentor status for GSoC and/or Outreachy
To: Molly de Blanc 
Cc: Sunil Mohan Adapa , Parent Pierre <
pierre.par...@insa-rouen.fr>


Cc: Sunil Mohan Adapa (mentor)
Cc: Pierre Parent (mentor)

On Wed, Mar 14, 2018 at 7:37 PM, Molly de Blanc  wrote:

>
> Additionally, we're looking to plan an IRC meeting to check in with
> everyone, using the channel #debian-soc-mentors (pw: dpldance). Please
> share your time zone and any times that work well for you. We understand
> it will be hard to find a time that works for everyone.
>

I think that creating a mailing list only for the mentors may be a good
idea,
besides the chatroom. The discussion in a mailing list is more structured
and does not have the problem of the time zones.


> 1. Your name
>

Dashamir Hoxha


> 2. Project name
>

1 - EasyGnuPG Improvements  (mentor, looking for co-mentors)
2 - Virtual LTSP Server (mentor, trying to find another mentor)
3 - Install FreedomBox in a Container (co-mentor, primary mentor: Sunil
Mohan Adapa)
4 - Own-Mailbox Improvements (co-mentor, primary mentor: Pierre Parent)


> 3. Are  you participating in GSoC or Outreachy with more than one
> organization?
>

I have proposed a project idea on Drupal GSoC as well.


> 4. Your time zone and times that work well for you.
>

Timezone: UTC+1 (CET)
Times: 08:00 - 22:00 (UTC)

Thanks,
Dashamir



>
> On Thu, Mar 15, 2018 at 12:07 AM, Molly de Blanc 
> wrote:
>
>> Dear Mentors,
>>
>> Greeting from Debian Outreach Team :)
>>
>> We are so thrilled to have you all as a part of Google Summer of Code
>> 2018and/or Outreachywith Debian.
>>
>> The student application period has already started and we are doing a
>> final role call to make sure that all mentors and co-mentors are still
>> available for their projects.We're asking all mentors to reconfirm by
>> responding to this email.
>>
>> Additionally, we're looking to plan an IRC meeting to check in with
>> everyone, using the channel #debian-soc-mentors (pw: dpldance). Please
>> share your time zone and any times that work well for you. We understand
>> it will be hard to find a time that works for everyone.
>>
>> In your email, please include:
>>
>> 1. Your name
>> 2. Project name
>> 3. Are  you participating in GSoC or Outreachy with more than one
>> organization?
>> 4. Your time zone and times that work well for you.
>>
>> Please send the reply by 15th March. On March 16th, we'll remove
>> projects without confirmed mentors.
>>
>> We will get back to you soon!
>>
>> Cheers,
>>
>> Your friendly Debian Outreach Team
>>
>>
>
>
> --
> Regards,
>
> Pranav Jain
>
>

Re: student wiki pages, tagging the pages

[殷啟聰 | Kai-Chung Yan]

Is it mandatory to also submit them on Debian's Wiki? Now that over 30 students 
have submitted their proposals using Google Docs, that would seem to me double 
work.

Jaminy Prabaharan 於 2018年03月17日 星期六 01:55 下午 寫道:
> Hi all,
>
> I have created a Debian wiki page for adding all the project submissions from 
> the students.
>
> https://wiki.debian.org/SummerOfCode2018-StudentApplications
>
> It would be great if all mentors suggest and help your students to add their 
> projects there.
>
> Feel free to reply to this mail if you have any doubts/ideas.
>
> Best Regards,
> Jaminy.
>
> On Tue, Feb 20, 2018 at 2:39 AM, Daniel Pocock  > wrote:
>
>
> Hi all,
>
> In the past, students created their applications on the wiki
>
> Now we also have processes for them to fill out details on the GSoC and
> Outreachy web sites but do we still want them to create a basic wiki
> page introducing themselves?
>
> Note that I'm not referring to pages with the project URL, only basic
> wiki user pages like https://wiki.debian.org/DanielPocock 
> 
>
> Asking students to put some categories on their page (e.g. a GSoC tag, a
> tag for their country) could help to quickly see a list of people in a
> particular country or school.  E.g. if we can see all the applicants in
> Brazil, somebody from the local community there may want to contact them
> about MiniDebConf in April, even if their mentor wasn't aware of that
> event and hadn't been able to tell them about it.
>
> https://wiki.debian.org/Brasil/Eventos/MiniDebConfCuritiba2018 
> 
>
> Regards,
>
> Daniel
>
>



signature.asc
Description: OpenPGP digital signature

Re: GSoC 2018 QA

[Chirayu Desai]

Hey Umang,

Thanks for your interest in our project! It is great that you have already
have some experience working with Java and Android. The kinds of things
we work are:

* Android Java programming
* building and managing Java jars
* C code and building with Makefiles
* how Debian works
* how to make Debian packages

We do not expect you to have all of these skills, but you'll need to be
strong in at least two to be an effective contributor. And of course
part of this is about you learning new skills.

Next steps for you are to look through the Android Tools team wiki to
learn about the project and what needs doing, and to put together your
application based on the questions in the project description.
https://wiki.debian.org/AndroidTools

For putting together your application, you can see the applications from
previous years to get an idea of what that should look like:
https://wiki.debian.org/SummerOfCode2016/StudentApplications

Feel free to ping any of us in IRC when you have questions.

Also ,in order to be outstanding among other candidates, it is highly
recommended that you make some contributions, no matter how big or small,
to our project prior to the selection phase.

You can also submit a draft proposal after you've done some reading and we
can read that and provide you with feedback.

On Fri, Mar 16, 2018 at 4:21 PM Umang Parmar  wrote:

> Hello everyone,
>
> I am Umang, currently enrolled in the 3rd year of B.Tech in Information
> and Communication Technology at DA-IICT, Gandhinagar, India.
> Out of all projects proposed by Debian, one idea namely "Android SDK
> Tools in Debian
> "
> interested me. I have some experience working with Java and Android and I
> am willing to learn more about it. I am thinking to submit a proposal for
> same project.
> So how should I prepare my proposal in order to increase chances of my
> acceptance?
>
>
>
> --
> Umang
>

Re: mentor:student ratios, team mentoring, etc

[Daniele Nicolodi]

On 17/03/2018 00:11, Daniel Powell wrote:
> I wrote a blog post with some input about how to structure mentorship
> teams from my experience as a service manager in automotive repair (of
> all things). I put it into a blog post here:
> 
> https://www.2kreate.com/index.html#Post-Mentorship

Hi Daniel,

I finally found the time to read you blog post [0].  I appreciate your
point of view.  Quoting from your blog post:

> I would, however, avoid assigning a mentor as a lead for a student
> in this format. It makes the barrier for reaching out to the other
> two mentors too high (especially for those who are relatively new to
> a team dynamic).

Why do you thing that having a lead mentor would inhibit students from
reaching out to the other mentors?  I don't think that student-mentors
communication should be mediated by the leas mentor.

I think that having someone responsible for the project, in the
"bookkeeping" sense, could be an advantage.  However, I'm mostly
familiar with the mentoring/supervising in academic context, and not at
all with the GSoC format, thus it may be the case that most things
should happen by initiative of the students and mentors are not supposed
to be actively checking over the progress of the project.

Cheers,
Dan

[0] You have a typo in the post: s/ass/as/

Re: mentor:student ratios, team mentoring, etc

[Daniel Powell]

Dan! Thank you.

Seems there are a lot of us Dan's going around. (I go by Daniel but am
often referred to as Dan).

>Why do you thing that having a lead mentor would inhibit students from
>reaching out to the other mentors?  I don't think that student-mentors
>communication should be mediated by the leas mentor.

I'm going to run through two scenarios that we had run into at a repair
shop that I used to manage. Keep in mind that it was ABSOLUTELY critical in
this environment to have an inexperienced technician ASK QUESTIONS when
they were uncertain about a repair procedure. So, this environment differed
somewhat from the software engineering atmosphere where critical vehicle
systems are not involved, but important parallels can still be drawn.

In both scenarios, we'll assume the following two things (for simplicity):

=> There are two mentors and one apprentice
=> There is a clash of personalities between one of the mentors and the
apprentice that causes the apprentice discomfort (Maybe we can imagine a
mentor who scoffs/scorns at questions).
=> The apprentice is new to team dynamics

*Scenario 1:*

A new apprentice is assigned directly to the mentor with whom he/she is not
comfortable with. During their first interaction, the apprentice asks a
question that seemed obvious to the mentor, and the response is interpreted
by the apprentice as rude or degrading (even if it wasn't actually).
Because the technician was assigned to the mentor, they are more likely to
avoid asking important questions/engaging in the mentoring process to avoid
discomfort, and by the end of the first week is frustrated, uncomfortable
and most importantly has not asked critical questions of the mentor. The
apprentice does not go to the other mentor to ask questions because he's
been assigned to a mentor and does not want to offend his mentor by
circumventing him.

*Scenario 2:*

A new apprentice is introduced to both mentors and told that he is free to
ask either for help. He has the same experience with mentor 1 as he did in
the first scenario. He runs across a critical issue and feels more
comfortable approaching the other mentor. He goes and asks mentor 2 for
help. It happens that mentor 1 is the specialist in this area, so mentor 2
(who probably knows that mentor 1 has less than ideal social filters and a
temper) has a short conversation with both mentor 1 and the apprentice (in
a software team this conversation would be an email to both parties/CC)
simply saying "Hey, mentor 1, I noticed the apprentice is struggling with
this. What is you input on how he should move forward?" and hands the
conversation over to mentor 1. If the question that the apprentice had was
silly or obvious, the 2nd mentor can help filter that out, or help phrase
the problem for mentor 1.

The difference in time allocation isn't much, mentor 1 still handles the
issue when it's in his expertise. Often times (in software engineering and
automotive repair) mentor 1 is older, more skilled and less tolerant of
stupid questions, mentor 2 is not a rookie, but not an expert and is more
tolerant because he can still remember what it's like to be wet behind the
ears. In essence, in scenario 2, the apprentice was still assigned to
mentor 1. He just didn't KNOW he was assigned to mentor 1, to increase his
ability to ask questions freely and comfortably. This subtle distinction
helps increase learnability within a mentoring program (measurably in
automotive repair - it decreases apprentice technician turnover within
their first 6 months and more importantly decreases critical errors.

Let me be clear: It may not be necessary or beneficial to apply these
principals to software development teams because it ISN'T critical like it
would be if the apprentice was repairing your mother's brake system. But,
there is something to be said about being more comfortable learning and
participating in the process. It may be worth trying on a small scale to
see if it improves outcomes. It may turn out that it's not for other
reasons, as you stated.

ALSO worth noting, is that the discomfort with working with someone wears
off quickly once an apprentice is used to working in team dynamics. In
other words: if an new/rookie technician has already worked in team
environments, it's likely that this wouldn't be as important. I noticed
that with those who have no experience with teams, this piece is absolutely
critical for the first 1-3 months.

Sorry if I drew that out far past the subjects' worthiness. Happy coding to
all!

Daniel Powell

On Mon, Mar 19, 2018 at 12:56 PM, Daniele Nicolodi 
wrote:

> On 17/03/2018 00:11, Daniel Powell wrote:
> > I wrote a blog post with some input about how to structure mentorship
> > teams from my experience as a service manager in automotive repair (of
> > all things). I put it into a blog post here:
> >
> > https://www.2kreate.com/index.html#Post-Mentorship
>
> Hi Daniel,
>
> I finally found the time to read you blog post [0].  I appreciate your
> point

Re: Tools for communication, coordination and project management

[Daniel Pocock]

On 10/03/18 07:37, Alexander Wirt wrote:
> On Sat, 10 Mar 2018, Dashamir Hoxha wrote:
> 
>> On Thu, Mar 8, 2018 at 4:38 AM, Jaminy Prabaharan 
>> wrote:
>>
>>>
>>> Seperate GitHub for debian-gsoc looks like better idea for the project
>>> management.
>>>
>>
>> I have created an organization on GitHub: https://github.com/debian-gsoc
>>>
>>> If someone would like to give it a try, please send me your GitHub
>> username, so that I can invite you.
> don't call it debian. 
> 


I met with Dashamir in Tirana and had a brief look at what he tried to
do with Github.

He has put a lot of time and thought into this and while it is not what
many mentors want to use, I feel that it is also really important in an
outreach program to assume that many of the people coming into the
program, which may include both students and mentors, have exposure to a
wide range of tools and may consider upgrading to things that are more free.

This thread is one of the reasons I created the wiki page mentioned in
another thread, but I feel it can also provide some closure for this
thread and help in future rounds:

https://wiki.debian.org/Teams/Outreach/Tools

Regards,

Daniel

Re: Tools for communication, coordination and project management

[Alexander Wirt]

On Mon, 19 Mar 2018, Daniel Pocock wrote:

> 
> 
> On 10/03/18 07:37, Alexander Wirt wrote:
> > On Sat, 10 Mar 2018, Dashamir Hoxha wrote:
> > 
> >> On Thu, Mar 8, 2018 at 4:38 AM, Jaminy Prabaharan 
> >> wrote:
> >>
> >>>
> >>> Seperate GitHub for debian-gsoc looks like better idea for the project
> >>> management.
> >>>
> >>
> >> I have created an organization on GitHub: https://github.com/debian-gsoc
> >>>
> >>> If someone would like to give it a try, please send me your GitHub
> >> username, so that I can invite you.
> > don't call it debian. 
> > 
> 
> 
> I met with Dashamir in Tirana and had a brief look at what he tried to
> do with Github.
> 
> He has put a lot of time and thought into this and while it is not what
> many mentors want to use, I feel that it is also really important in an
> outreach program to assume that many of the people coming into the
> program, which may include both students and mentors, have exposure to a
> wide range of tools and may consider upgrading to things that are more free.
> 
> This thread is one of the reasons I created the wiki page mentioned in
> another thread, but I feel it can also provide some closure for this
> thread and help in future rounds:
> 
> https://wiki.debian.org/Teams/Outreach/Tools
That doesn't change anything about that thing not being "Debian". 

Alex
 

Re: Tools for communication, coordination and project management

[Daniel Pocock]

On 19/03/18 22:33, Alexander Wirt wrote:
> On Mon, 19 Mar 2018, Daniel Pocock wrote:
> 
>>
>>
>> On 10/03/18 07:37, Alexander Wirt wrote:
>>> On Sat, 10 Mar 2018, Dashamir Hoxha wrote:
>>>
 On Thu, Mar 8, 2018 at 4:38 AM, Jaminy Prabaharan 
 wrote:

>
> Seperate GitHub for debian-gsoc looks like better idea for the project
> management.
>

 I have created an organization on GitHub: https://github.com/debian-gsoc
>
> If someone would like to give it a try, please send me your GitHub
 username, so that I can invite you.
>>> don't call it debian. 
>>>
>>
>>
>> I met with Dashamir in Tirana and had a brief look at what he tried to
>> do with Github.
>>
>> He has put a lot of time and thought into this and while it is not what
>> many mentors want to use, I feel that it is also really important in an
>> outreach program to assume that many of the people coming into the
>> program, which may include both students and mentors, have exposure to a
>> wide range of tools and may consider upgrading to things that are more free.
>>
>> This thread is one of the reasons I created the wiki page mentioned in
>> another thread, but I feel it can also provide some closure for this
>> thread and help in future rounds:
>>
>> https://wiki.debian.org/Teams/Outreach/Tools
> That doesn't change anything about that thing not being "Debian". 
> 

I'm completely in agreement with you

On the other hand, I've given several talks recently where I've reminded
people they are free to create "Daniel Pocock" profiles on Facebook and
Twitter.  We can't control what people do on other platforms, we can
only try to celebrate what is great about our own.

Regards,

Daniel

email to debian-devel-announce?

[Daniel Pocock]

Hi all,

I realized we never sent anything to debian-devel-announce this year.

Is there anybody in the team keen to send such an email?

As mentioned in my blog[1] today, I feel it would be good for more
people to look over all the applicants, including those who proposed
their own topics.

If there is a preference to be more restrictive on the number of slots
this year, then maybe we could also ask if there are people from the
wider community who want to be part of a selection committee without
becoming mentors?

Are there any other points that belong in such an email?

Regards,

Daniel


1. https://danielpocock.com/mentors-dont-need-to-be-debian-developers

Re: Tools for communication, coordination and project management

[Daniele Nicolodi]

On 3/19/18 3:38 PM, Daniel Pocock wrote:
> On 19/03/18 22:33, Alexander Wirt wrote:
>>
>> That doesn't change anything about that thing not being "Debian". 
> 
> I'm completely in agreement with you
> 
> On the other hand, I've given several talks recently where I've reminded
> people they are free to create "Daniel Pocock" profiles on Facebook and
> Twitter.  We can't control what people do on other platforms, we can
> only try to celebrate what is great about our own.

I'm not suggesting that this applies to the case at hand, however I
don't think this is completely true:

https://www.debian.org/trademark

In particular:
1. You cannot use Debian trademarks in any way that suggests an
  affiliation with or endorsement by the Debian project or community,
  if the same is not true.
  2. You cannot use Debian trademarks in a company or organization name or
  as the name of a product or service.

Cheers,
Dan

Re: GSoC 2018 QA

[Umang Parmar]

Thank you for your reply.
I had one more question. Do I need to create my wiki page on debian with
project proposal or will google document link suffice?

-
Umang


On Mon 19 Mar, 2018, 21:49 Chirayu Desai,  wrote:

> Hey Umang,
>
> Thanks for your interest in our project! It is great that you have already
> have some experience working with Java and Android. The kinds of things
> we work are:
>
> * Android Java programming
> * building and managing Java jars
> * C code and building with Makefiles
> * how Debian works
> * how to make Debian packages
>
> We do not expect you to have all of these skills, but you'll need to be
> strong in at least two to be an effective contributor. And of course
> part of this is about you learning new skills.
>
> Next steps for you are to look through the Android Tools team wiki to
> learn about the project and what needs doing, and to put together your
> application based on the questions in the project description.
> https://wiki.debian.org/AndroidTools
>
> For putting together your application, you can see the applications from
> previous years to get an idea of what that should look like:
> https://wiki.debian.org/SummerOfCode2016/StudentApplications
>
> Feel free to ping any of us in IRC when you have questions.
>
> Also ,in order to be outstanding among other candidates, it is highly
> recommended that you make some contributions, no matter how big or small,
> to our project prior to the selection phase.
>
> You can also submit a draft proposal after you've done some reading and we
> can read that and provide you with feedback.
>
> On Fri, Mar 16, 2018 at 4:21 PM Umang Parmar 
> wrote:
>
>> Hello everyone,
>>
>> I am Umang, currently enrolled in the 3rd year of B.Tech in Information
>> and Communication Technology at DA-IICT, Gandhinagar, India.
>> Out of all projects proposed by Debian, one idea namely "Android SDK
>> Tools in Debian
>> "
>> interested me. I have some experience working with Java and Android and I
>> am willing to learn more about it. I am thinking to submit a proposal for
>> same project.
>> So how should I prepare my proposal in order to increase chances of my
>> acceptance?
>>
>>
>>
>> --
>> Umang
>>
>

Re: GSoC 2018 QA

[Chirayu Desai]

I believe at this point just the Google document will suffice. We can
review it once you upload and give feedback.

On Tue, Mar 20, 2018, 07:16 Umang Parmar  wrote:

> Thank you for your reply.
> I had one more question. Do I need to create my wiki page on debian with
> project proposal or will google document link suffice?
>
> -
> Umang
>
>
> On Mon 19 Mar, 2018, 21:49 Chirayu Desai,  wrote:
>
>> Hey Umang,
>>
>> Thanks for your interest in our project! It is great that you have already
>> have some experience working with Java and Android. The kinds of things
>> we work are:
>>
>> * Android Java programming
>> * building and managing Java jars
>> * C code and building with Makefiles
>> * how Debian works
>> * how to make Debian packages
>>
>> We do not expect you to have all of these skills, but you'll need to be
>> strong in at least two to be an effective contributor. And of course
>> part of this is about you learning new skills.
>>
>> Next steps for you are to look through the Android Tools team wiki to
>> learn about the project and what needs doing, and to put together your
>> application based on the questions in the project description.
>> https://wiki.debian.org/AndroidTools
>>
>> For putting together your application, you can see the applications from
>> previous years to get an idea of what that should look like:
>> https://wiki.debian.org/SummerOfCode2016/StudentApplications
>>
>> Feel free to ping any of us in IRC when you have questions.
>>
>> Also ,in order to be outstanding among other candidates, it is highly
>> recommended that you make some contributions, no matter how big or small,
>> to our project prior to the selection phase.
>>
>> You can also submit a draft proposal after you've done some reading and
>> we can read that and provide you with feedback.
>>
>> On Fri, Mar 16, 2018 at 4:21 PM Umang Parmar 
>> wrote:
>>
>>> Hello everyone,
>>>
>>> I am Umang, currently enrolled in the 3rd year of B.Tech in Information
>>> and Communication Technology at DA-IICT, Gandhinagar, India.
>>> Out of all projects proposed by Debian, one idea namely "Android SDK
>>> Tools in Debian
>>> "
>>> interested me. I have some experience working with Java and Android and I
>>> am willing to learn more about it. I am thinking to submit a proposal for
>>> same project.
>>> So how should I prepare my proposal in order to increase chances of my
>>> acceptance?
>>>
>>>
>>>
>>> --
>>> Umang
>>>
>>