9 Oct
2013
9 Oct
'13
3:17 p.m.
Dear All
GSoc 2014 has been announced. Cheers to it.
We have learnt a lot over the past few months and will like to propose
a set of guidelines, please let us know of your opinions
1. If the student is not writing weekly reports and the mentor fails
the student, we wont accept the evaluations as PASS or go to Google
for reevaluations.
2. GSoC is supposed to be a full time project. If the work is done
earlier, it is upto the mentor to decide if he or she will get more
work or not.
3. Students must have committed some code / package or some other form
of contribution to openSUSE.
4. Students are expeceted to work atleast 4 hours a day (it will
usually mean atleast 2 pull requests / commits as a bare minimum per
week)
5. Students should be verified by a college professor vouching for him.
6. Mentors should encourage kick off meetings
If this is ok with you guys, I will add it to the wiki.
--
Regards
Manu Gupta
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
9 Oct
9 Oct
3:36 p.m.
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta <manugupt1(a)gmail.com> wrote:
3. Students must have committed some code / package or
some other form
of contribution to openSUSE.
Is anything specifically related to packaging appropriate? The GSoC
sponsorships are for coding not packaging. If a student knows nothing
about packaging what are they supposed to do?
Do most of the sponsored programs involve code living in a SCCR system
under openSUSE's umbrella?
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
10 Oct
10 Oct
11:55 a.m.
Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote:
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form
of contribution to openSUSE. prior to GSoC. This sounds better I believe
The idea is to get in more contributions and bootstrap students to
openSUSE rather than waiting for the GSoC timelines.
3. Students must have committed some code /
package or some other form
of contribution to openSUSE.
Is anything specifically related to packaging
appropriate? The GSoC
sponsorships are for coding not packaging. If a student knows nothing
about packaging what are they supposed to do?
Yes, but a few organizations have it. I am not sure if we will take in
packaging related tasks, but we should not completely turn them down.
Code related tasks will be of higher priority usually.
Fedora had it in 2011, a packaging related project
http://www.google-melange.com/gsoc/project/google/gsoc2011/sanjay_ankur/140…
Do most of the sponsored programs involve code living
in a SCCR system
under openSUSE's umbrella?
I am not sure what do you mean by SCCR system, sorry, can you explain it?
Greg
--
Greg Freemyer
--
Regards
Manu Gupta
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
2:07 p.m.
On Thu, Oct 10, 2013 at 12:55 PM, Manu Gupta <manugupt1(a)gmail.com> wrote:
SCCR - Source Code Control Repository.
I guess my question is if most of the GCoC projects involve work on
projects for which openSUSE is the upstream provider.
Greg
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote:
How about:
3. Students must have contributed to openSUSE prior to being accepted
by openSUSE for GSoC participation. As with openSUSE team members,
contribution can be of many forms, but those applicants with a history
of supporting openSUSE packaging efforts and/or committing code
changes to projects where openSUSE is the upstream will be given
preference at the time of final selection.
fyi: Is that a realistic requirement? What percentage of past
awardees would have met that requirement?
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form
of contribution to openSUSE. prior to GSoC. This sounds better I believe 3. Students must have committed some code /
package or some other form
of contribution to openSUSE.
The idea is to get in more contributions and bootstrap
students to
openSUSE rather than waiting for the GSoC timelines.
Very interesting. I proposed a packaging related project a couple
years ago and was told it wasn't appropriate.
For a project like openSUSE, packaging seems like it would be a great
GSoC project if Google is okay with it.
Is anything specifically related to packaging
appropriate? The GSoC
sponsorships are for coding not packaging. If a student knows nothing
about packaging what are they supposed to do?
Yes, but a few organizations have it. I am not sure if we will take in
packaging related tasks, but we should not completely turn them down.
Code related tasks will be of higher priority usually.
Fedora had it in 2011, a packaging related project
http://www.google-melange.com/gsoc/project/google/gsoc2011/sanjay_ankur/140… Do most of the
sponsored programs involve code living in a SCCR system
under openSUSE's umbrella?
I am not sure what do you mean by SCCR system, sorry, can you explain it? 
7:08 p.m.
On 10/10/2013 03:07 PM, Greg Freemyer wrote:
On Thu, Oct 10, 2013 at 12:55 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
Well, I think it depends on the scale of the package. For example I
mentored a project (Eucalyptus and CloudStack) which was heavily biased
toward packaging. But there was also stuff to learn about cloud
framework implementation and eventually image building and documentation.
With the exception of my student getting seriously ill, that worked
pretty well. Packaging is part of what we do, as mentioned earlier thus
it should not be excluded. But having a project that syas "package all
of CPAN" (yes, we have automation, it's just an example, lets not split
hairs) would not be going in the right direction, IMHO.
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote:
How about:
3. Students must have contributed to openSUSE prior to being accepted
by openSUSE for GSoC participation. As with openSUSE team members,
contribution can be of many forms, but those applicants with a history
of supporting openSUSE packaging efforts and/or committing code
changes to projects where openSUSE is the upstream will be given
preference at the time of final selection.
fyi: Is that a realistic requirement? What percentage of past
awardees would have met that requirement?
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form
of contribution to openSUSE. prior to GSoC. This sounds better I believe 3. Students must have committed some code /
package or some other form
of contribution to openSUSE.
The idea is to get in more contributions and
bootstrap students to
openSUSE rather than waiting for the GSoC timelines.
Very interesting. I proposed a packaging related project a couple
years ago and was told it wasn't appropriate.
For a project like openSUSE, packaging seems like it would be a great
GSoC project if Google is okay with it. Is anything specifically related to packaging
appropriate? The GSoC
sponsorships are for coding not packaging. If a student knows nothing
about packaging what are they supposed to do?
Yes, but a few organizations have it. I am not sure if we will take in
packaging related tasks, but we should not completely turn them down.
Code related tasks will be of higher priority usually.
Fedora had it in 2011, a packaging related project
http://www.google-melange.com/gsoc/project/google/gsoc2011/sanjay_ankur/140…
7:03 p.m.
On 10/10/2013 12:55 PM, Manu Gupta wrote:
Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote:
Well it still sounds as if we are only interested in students that
already contribute to openSUSE. IMHO, GSoC is a good way for us to gain
new contributors. Therefore I am not much in favor of such a string
statement.
How about this:
3.) Students that already contribute to openSUSE are encouraged to
participate.
This does not exclude/discourage students that are not already part of
the project and encourages those that already contribute to not ignore
the opportunity of getting paid for their work, for a little while ;)
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form
of contribution to openSUSE. prior to GSoC. This sounds better I believe 3. Students must have committed some code /
package or some other form
of contribution to openSUSE.
11:05 p.m.
On Thu, 10 Oct 2013 20:03:31 -0400
Robert Schweikert <rjschwei(a)suse.com> wrote:
3.) Students that already contribute to openSUSE are
encouraged to
participate.
Also, in case that same project will have more than one candidate,
student that already participate in openSUSE will have advantage,
specially if GSoC project is natural extension of his prior activity.
This does not exclude newcomers, but gives incentive to be active,
plan for the future and when time comes, just add GSoC project to
the regular activity.
This also opens opportunity to work on a bigger projects then GSoC time
frame allows.
--
Regards, Rajko.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
11 Oct
11 Oct
12:43 a.m.
Hi,
I think we should *prefer* students prior contributions, as there will
be a better chance of them sticking around after the end of the
program. This year, we had a heady mix of people with prior
contributions and newcomers. This would be preferable.
Regards,.
Saurabh
On Fri, Oct 11, 2013 at 9:35 AM, Rajko <rmatov101(a)charter.net> wrote:
On Thu, 10 Oct 2013 20:03:31 -0400
Robert Schweikert <rjschwei(a)suse.com> wrote:
--
Regards,.
Saurabh Sood
Have a lot of fun!
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
3.) Students that already contribute to openSUSE
are encouraged to
participate.
Also, in case that same project will have more than one candidate,
student that already participate in openSUSE will have advantage,
specially if GSoC project is natural extension of his prior activity.
This does not exclude newcomers, but gives incentive to be active,
plan for the future and when time comes, just add GSoC project to
the regular activity.
This also opens opportunity to work on a bigger projects then GSoC time
frame allows.
--
Regards, Rajko.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
9:52 a.m.
On 10/11/2013 01:43 AM, Saurabh Sood wrote:
Hi,
I think we should *prefer* students prior contributions, as there will
be a better chance of them sticking around after the end of the
program. This year, we had a heady mix of people with prior
contributions and newcomers. This would be preferable.
There is nothing in the proposed new wording that precludes the
preference of existing contributors. However, the original proposal for
#3 was very strong in discouraging newcomers to apply for GSoC projects
in openSUSE.
First, actively discouraging participation via strongly worded
guidelines as originally proposed is against our guiding principals.
Secondly, if we only consider students that already contribute how are
we ever going to grow.
I don't think anyone has an issue with giving a student that already
contributes to the project and has an equally strong plan and proposal
as a newcomer the advantage. However as was originally proposed you
might as well have written "Newcomers don't apply", and that is
something I and others have an issue with.
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
6:13 a.m.
Hey,
On 11.10.2013 02:03, Robert Schweikert wrote:
On 10/10/2013 12:55 PM, Manu Gupta wrote:
Me neither, GSoC is especially useful for newcommers. I think the goal
you want to reach Manu is a set of guidelines for the mentors, not for
students. You should differentiate the two.
Henne
--
Henne Vogelsang
http://www.opensuse.org
Everybody has a plan, until they get hit.
- Mike Tyson
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote:
GSoC is a good way for us to gain
new contributors. Therefore I am not much in favor of such a string
statement. On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form
of contribution to openSUSE. prior to GSoC. This sounds better I believe 3. Students must have committed some code /
package or some other form
of contribution to openSUSE.
9:53 a.m.
On 10/11/2013 07:13 AM, Henne Vogelsang wrote:
Hey,
On 11.10.2013 02:03, Robert Schweikert wrote:
Agreed on the "we should have guidelines for mentors" part, but I do
think some (additional) guidelines for students to set expectation are
very useful as well.
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On 10/10/2013 12:55 PM, Manu Gupta wrote:
Me neither, GSoC is especially useful for newcommers. I think the goal
you want to reach Manu is a set of guidelines for the mentors, not for
students. You should differentiate the two. Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote:
GSoC is a good way for us to gain
new contributors. Therefore I am not much in favor of such a string
statement. On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
> 3. Students must have committed some code / package or some other form
> of contribution to openSUSE.
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form
of contribution to openSUSE. prior to GSoC. This sounds better I believe
12 Oct
12 Oct
2:55 a.m.
Hey,
Sorry for the top-posting
Yes, it was general, maybe we should separate it out. I dont know
How does this sound ?
3. Students are highly encouraged have committed some code / package
or some other form of contribution to openSUSE prior to GSoC. This
will help new comers familiarize with the community before GSoC and
also give ample time to mentors and the community to know the student.
Knowing people around you is a good way to start off and also
strengthen final GSoC proposals.
On Fri, Oct 11, 2013 at 8:23 PM, Robert Schweikert <rjschwei(a)suse.com> wrote:
On 10/11/2013 07:13 AM, Henne Vogelsang wrote:
--
Regards
Manu Gupta
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hey,
On 11.10.2013 02:03, Robert Schweikert wrote:
Agreed on the "we should have guidelines for mentors" part, but I do think
some (additional) guidelines for students to set expectation are very useful
as well.
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On 10/10/2013 12:55 PM, Manu Gupta wrote:
Me neither, GSoC is especially useful for newcommers. I think the goal
you want to reach Manu is a set of guidelines for the mentors, not for
students. You should differentiate the two.
Hi Greg,
On Thu, Oct 10, 2013 at 2:06 AM, Greg Freemyer <greg.freemyer(a)gmail.com>
wrote:
>
> On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta <manugupt1(a)gmail.com> wrote:
>>
>> 3. Students must have committed some code / package or some other form
>> of contribution to openSUSE.
>
>
I should add Prior to GSoC here.
3. Students must have committed some code / package or some other form
of contribution to openSUSE. prior to GSoC. This sounds better I believe
GSoC is a good way for us to gain
new contributors. Therefore I am not much in favor of such a string
statement.
17 Oct
17 Oct
7:48 a.m.
On 10/12/2013 03:55 AM, Manu Gupta wrote:
Hey,
Sorry for the top-posting
Yes, it was general, maybe we should separate it out. I dont know
How does this sound ?
3. Students are highly encouraged have committed some code / package
or some other form of contribution to openSUSE prior to GSoC. This
will help new comers familiarize with the community before GSoC and
also give ample time to mentors and the community to know the student.
Knowing people around you is a good way to start off and also
strengthen final GSoC proposals.
Sounds good to me. I'd leave out "highly", i.e "Students are encouraged
to....."
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
8:02 a.m.
On Thu, Oct 17, 2013 at 8:48 AM, Robert Schweikert <rjschwei(a)suse.com> wrote:
On 10/12/2013 03:55 AM, Manu Gupta wrote:
fyi: if it's down to grammar
"help new comers familiarize with the community:
should be
"help newcomers familiarize themselves with the community"
Greg
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hey,
Sorry for the top-posting
Yes, it was general, maybe we should separate it out. I dont know
How does this sound ?
3. Students are highly encouraged have committed some code / package
or some other form of contribution to openSUSE prior to GSoC. This
will help new comers familiarize with the community before GSoC and
also give ample time to mentors and the community to know the student.
Knowing people around you is a good way to start off and also
strengthen final GSoC proposals.
Sounds good to me. I'd leave out "highly", i.e "Students are
encouraged
to....."
10 Oct
10 Oct
6:59 p.m.
On 10/09/2013 04:36 PM, Greg Freemyer wrote:
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta
<manugupt1(a)gmail.com> wrote:
Learn ;)
We are a distribution, packaging is part of what we do. I have been
working a lot with people that generally live outside the packaging
world lately and I can only say that we need more people that realize
that packaging is a very important part of the Linux world.
That does not imply that I think students should just create a bunch of
packages, that is probably a bit too simple.
Later
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
3. Students must have committed some code /
package or some other form
of contribution to openSUSE.
Is anything specifically related to packaging appropriate? The GSoC
sponsorships are for coding not packaging. If a student knows nothing
about packaging what are they supposed to do?
9 Oct
9 Oct
3:45 p.m.
Manu (dropping project),
A library that allows access to NTFS VSCs( volume shadow copies) is
part of 13.1 for the first time (libvshadow). I don't think any other
distro has it included yet. VSCs are similar to BtrFS snapshots at
least to some extent. (I know far more about VSCs than I do BtrFS
snapshots).
I think a great SoC project would be to do one of the following:
- write a GUI front-end that would mount the volume shadow copies in
/media or /run, etc. I guess it could be a new YaST module.
- integrate libvshadow into a filemanager such KDE's dolphin or mc
(midnight commander)
- integrate libvshadow into snapper (I'm not sure this makes since.
VSCs are readonly from Linux. They only change if the user is dual
booting to Windows.)
Are either of the above appropriate openSUSE GSoC ideas? I think the
scope of the projects are about right, but I'm not sure they are
openSUSE specific enough.
Thanks
Greg
--
Greg Freemyer
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta <manugupt1(a)gmail.com> wrote:
Dear All
GSoc 2014 has been announced. Cheers to it.
We have learnt a lot over the past few months and will like to propose
a set of guidelines, please let us know of your opinions
1. If the student is not writing weekly reports and the mentor fails
the student, we wont accept the evaluations as PASS or go to Google
for reevaluations.
2. GSoC is supposed to be a full time project. If the work is done
earlier, it is upto the mentor to decide if he or she will get more
work or not.
3. Students must have committed some code / package or some other form
of contribution to openSUSE.
4. Students are expeceted to work atleast 4 hours a day (it will
usually mean atleast 2 pull requests / commits as a bare minimum per
week)
5. Students should be verified by a college professor vouching for him.
6. Mentors should encourage kick off meetings
If this is ok with you guys, I will add it to the wiki.
--
Regards
Manu Gupta
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
10 Oct
10 Oct
11:57 a.m.
On Thu, Oct 10, 2013 at 2:15 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote:
Manu (dropping project),
A library that allows access to NTFS VSCs( volume shadow copies) is
part of 13.1 for the first time (libvshadow). I don't think any other
distro has it included yet. VSCs are similar to BtrFS snapshots at
least to some extent. (I know far more about VSCs than I do BtrFS
snapshots).
I think a great SoC project would be to do one of the following:
- write a GUI front-end that would mount the volume shadow copies in
/media or /run, etc. I guess it could be a new YaST module.
- integrate libvshadow into a filemanager such KDE's dolphin or mc
(midnight commander)
- integrate libvshadow into snapper (I'm not sure this makes since.
VSCs are readonly from Linux. They only change if the user is dual
booting to Windows.)
Are either of the above appropriate openSUSE GSoC ideas? I think the
scope of the projects are about right, but I'm not sure they are
openSUSE specific enough.
We encourage projects that are also beyond the scope of openSUSE
directly and all of them sound great ideas to me, it is just the
mentor who should have time.
Thanks
Greg
--
Greg Freemyer
On Wed, Oct 9, 2013 at 4:17 PM, Manu Gupta <manugupt1(a)gmail.com> wrote:
--
Regards
Manu Gupta
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Dear All
GSoc 2014 has been announced. Cheers to it.
We have learnt a lot over the past few months and will like to propose
a set of guidelines, please let us know of your opinions
1. If the student is not writing weekly reports and the mentor fails
the student, we wont accept the evaluations as PASS or go to Google
for reevaluations.
2. GSoC is supposed to be a full time project. If the work is done
earlier, it is upto the mentor to decide if he or she will get more
work or not.
3. Students must have committed some code / package or some other form
of contribution to openSUSE.
4. Students are expeceted to work atleast 4 hours a day (it will
usually mean atleast 2 pull requests / commits as a bare minimum per
week)
5. Students should be verified by a college professor vouching for him.
6. Mentors should encourage kick off meetings
If this is ok with you guys, I will add it to the wiki.
--
Regards
Manu Gupta
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
11:59 a.m.
On Thu, Oct 10, 2013 at 12:57 PM, Manu Gupta <manugupt1(a)gmail.com> wrote:
On Thu, Oct 10, 2013 at 2:15 AM, Greg Freemyer
<greg.freemyer(a)gmail.com> wrote:
I'll add them to the ideas page when it goes live.
Greg
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Manu (dropping project),
A library that allows access to NTFS VSCs( volume shadow copies) is
part of 13.1 for the first time (libvshadow). I don't think any other
distro has it included yet. VSCs are similar to BtrFS snapshots at
least to some extent. (I know far more about VSCs than I do BtrFS
snapshots).
I think a great SoC project would be to do one of the following:
- write a GUI front-end that would mount the volume shadow copies in
/media or /run, etc. I guess it could be a new YaST module.
- integrate libvshadow into a filemanager such KDE's dolphin or mc
(midnight commander)
- integrate libvshadow into snapper (I'm not sure this makes since.
VSCs are readonly from Linux. They only change if the user is dual
booting to Windows.)
Are either of the above appropriate openSUSE GSoC ideas? I think the
scope of the projects are about right, but I'm not sure they are
openSUSE specific enough.
We encourage projects that are also beyond the scope of openSUSE
directly and all of them sound great ideas to me, it is just the
mentor who should have time.
2693
days inactive
2701
days old
17 comments
6 participants
participants (6)
-
Greg Freemyer -
Henne Vogelsang -
Manu Gupta -
Rajko -
Robert Schweikert -
Saurabh Sood