[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] Atomic & GSoC via the CentOS Project



On Thu, Feb 19, 2015 at 4:03 PM, Karsten Wade <kwade redhat com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Folks:
>
> We're collecting ideas (over the next 24 hours) for work that Google
> Summer of Code students can do via the CentOS Project. In the past
> I've had good success with doing work with GSoC students via the
> Fedora Project where the work happens primarily in the upstream
> project, as long as it lands back with the distro.  We think the same
> can work for CentOS SIGs.
>
> For the Atomic SIG we're looking for items that might be directly or
> indirectly related to work needed in your SIG. It could be integration,
> packaging, or any other code-related task.
>
> Each idea needs to be associated with a mentor, but we can be flexible
> about the final mentor assignment once we (hopefully) get accepted to
> this year's GSoC.
>
> You can see the template of what we need to fill out for each
> idea.
>
> http://wiki.centos.org/GSoC/2015/Ideas
>
> Remember that these are tasks for e.g. computer science students, and
> a part of the work for the mentor is simply getting the student able
> to effectively contribute and collaborate in an open community. This
> means you can take an idea you might do over two months and split it
> in to 4 parts for 4 different students, etc.

There wasn't a whole lot of discussion about it in the original
thread, but I thought it might be an interesting project for a student
to chase down.

The thread that started here:
    https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-February/msg00016.html

Which ended up with the PoC here:
    https://github.com/maxamillion/docker-image-strip

Realistically this might depend on the Python3 EPEL work[0] if we can'
t get a bug fix sorted out for Python 2.7.x[1]

The GSoC proposal would need some work to define objectives for the
student to work on to define scope of project work and quantifiers for
success/failure of the student's work. I have a couple ideas around
that but would be open to others brainstorming.

It might be a bit off in the weeds of a proposal but I thought I'd
bring it up and see what others thought.

Thanks,
-AdamM


[0] - https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1194473


>
> Thanks - Karsten
> - --
> Karsten 'quaid' Wade        .^\          CentOS Doer of Stuff
> http://TheOpenSourceWay.org    \  http://community.redhat.com
> @quaid (identi.ca/twitter/IRC)  \v'             gpg: AD0E0C41
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iEYEARECAAYFAlTmXZgACgkQ2ZIOBq0ODEGe4gCfdsqAuDU0Hf1z2zciCm2LpgIU
> zOcAnR6p8zEBEMPQfA9VVxf0Nr9q62ec
> =EpkG
> -----END PGP SIGNATURE-----
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]