[prev in list] [next in list] [prev in thread] [next in thread]
List: fop-dev
Subject: Re: Google Summer of Code
From: Glenn Adams <glenn () skynav ! com>
Date: 2012-03-05 14:36:06
Message-ID: CACQ=j+cEDpawoCb3Ff6odgfQc0ZvPurZdXOkwdB4t14x28OqHQ () mail ! gmail ! com
[Download RAW message or body]
I would suggest whittling down the fop bug list, starting from the
beginning.
On Mon, Mar 5, 2012 at 6:35 AM, mehdi houshmand <med1985@gmail.com> wrote:
> Because of the overwhelming popularity of this idea, I've created a
> link on the Wiki
> (http://wiki.apache.org/xmlgraphics-fop/GoogleSummerOfCode2012) for
> the GSoC proposals.
>
> On a serious note, this is literally work for free. Google pays the
> bills and I'm happy to mentor any applicants and do the admin, all you
> have to do is provide ideas for projects. If you have a wish list or a
> list of TODOs that you think a newbie could do for a summer project (I
> do appreciate that's quite a big caveat), now's your opportunity.
>
> Mehdi
>
> On 1 March 2012 16:26, mehdi houshmand <med1985@gmail.com> wrote:
> > Hi Glenn,
> >
> > The GSoC doesn't relate directly to the ASF or FOP directly, however,
> > putting a few FOP projects as proposals would be a good way to get
> > some new interest into the project. I think it would be good for us as
> > we benefit from any work done, and it helps whomever does the work
> > learn the various skills that we as a community can impart upon them.
> >
> > I've included a link to the GSoC below, but if you do some research,
> > there's plenty of information out there.
> >
> > http://code.google.com/soc/
> >
> > Mehdi
> >
> > On 1 March 2012 16:13, Glenn Adams <glenn@skynav.com> wrote:
> >> could you provide a link to the "Google Summer of Code Project"? how
> does it
> >> relate to ASF and FOP activities?
> >>
> >>
> >> On Thu, Mar 1, 2012 at 3:50 AM, mehdi houshmand <med1985@gmail.com>
> wrote:
> >>>
> >>> Hi,
> >>>
> >>> We're thinking of submitting a proposal or two to the Google Summer of
> >>> Code project and wanted to get some input from the community on ideas.
> >>> Once we've got a few proposals I'll create a wiki page and put all the
> >>> ideas on there, but for now I just wanted to gauge interest.
> >>>
> >>> In terms of mentoring, I'm happy to be a mentor and I've registered as
> >>> one and if any other committers fancy the job, do register, the more
> >>> the merrier. The deadline is 9th March, so that doesn't give us long
> >>> to bounce around ideas, but here are a few I was thinking:
> >>>
> >>> - There have been recent discussions between Jeremias, myself and
> >>> others about extracting the Fonts packages into their own library. I
> >>> think this would be a great idea for a project because essentially it
> >>> only involves a few, well defined specifications (TTF, Type1 etc) and
> >>> doesn't expose the person to too much complexity. The way I'd suggest
> >>> this to be done, is by re-writing rather than porting, that way it
> >>> gives the person much more flexibility and also the current code would
> >>> give them good tips and tricks on how to deal with parsing fonts.
> >>>
> >>> - TTF in AFP. I know we still have the TrueTypeInPostScript branch
> >>> flying around, and however much I'd like to fob that onto someone
> >>> else, I don't think it's fair to do so. I have no idea how long this
> >>> project would take, but I think FOP could really benefit from it.
> >>> Currently we're forcing users to use AFP fonts for AFP documents, a
> >>> lot of which are archaic and use EBCDIC, for those of you who haven't
> >>> been exposed to EBCDIC, count yourself lucky.
> >>>
> >>> There may be something to do with PCL?? I'm not at all familiar with
> >>> the format, but I do remember discussions about upgrading to a newer
> >>> PCL standard? I'd be happy to acquaint myself with the format if
> >>> there's interest in the idea.
> >>>
> >>> Hopefully we can get a proposal together in time.
> >>>
> >>> Mehdi
> >>
> >>
>
[Attachment #3 (text/html)]
I would suggest whittling down the fop bug list, starting from the \
beginning.<br><br><div class="gmail_quote">On Mon, Mar 5, 2012 at 6:35 AM, mehdi \
houshmand <span dir="ltr"><<a \
href="mailto:med1985@gmail.com">med1985@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Because of the overwhelming popularity of this idea, I've \
created a<br> link on the Wiki<br>
(<a href="http://wiki.apache.org/xmlgraphics-fop/GoogleSummerOfCode2012" \
target="_blank">http://wiki.apache.org/xmlgraphics-fop/GoogleSummerOfCode2012</a>) \
for<br> the GSoC proposals.<br>
<br>
On a serious note, this is literally work for free. Google pays the<br>
bills and I'm happy to mentor any applicants and do the admin, all you<br>
have to do is provide ideas for projects. If you have a wish list or a<br>
list of TODOs that you think a newbie could do for a summer project (I<br>
do appreciate that's quite a big caveat), now's your opportunity.<br>
<span class="HOEnZb"><font color="#888888"><br>
Mehdi<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 1 March 2012 16:26, mehdi houshmand <<a \
href="mailto:med1985@gmail.com">med1985@gmail.com</a>> wrote:<br> > Hi \
Glenn,<br> ><br>
> The GSoC doesn't relate directly to the ASF or FOP directly, however,<br>
> putting a few FOP projects as proposals would be a good way to get<br>
> some new interest into the project. I think it would be good for us as<br>
> we benefit from any work done, and it helps whomever does the work<br>
> learn the various skills that we as a community can impart upon them.<br>
><br>
> I've included a link to the GSoC below, but if you do some research,<br>
> there's plenty of information out there.<br>
><br>
> <a href="http://code.google.com/soc/" \
target="_blank">http://code.google.com/soc/</a><br> ><br>
> Mehdi<br>
><br>
> On 1 March 2012 16:13, Glenn Adams <<a \
href="mailto:glenn@skynav.com">glenn@skynav.com</a>> wrote:<br> >> could you \
provide a link to the "Google Summer of Code Project"? how does it<br> \
>> relate to ASF and FOP activities?<br> >><br>
>><br>
>> On Thu, Mar 1, 2012 at 3:50 AM, mehdi houshmand <<a \
href="mailto:med1985@gmail.com">med1985@gmail.com</a>> wrote:<br> >>><br>
>>> Hi,<br>
>>><br>
>>> We're thinking of submitting a proposal or two to the Google Summer \
of<br> >>> Code project and wanted to get some input from the community on \
ideas.<br> >>> Once we've got a few proposals I'll create a wiki \
page and put all the<br> >>> ideas on there, but for now I just wanted to \
gauge interest.<br> >>><br>
>>> In terms of mentoring, I'm happy to be a mentor and I've \
registered as<br> >>> one and if any other committers fancy the job, do \
register, the more<br> >>> the merrier. The deadline is 9th March, so that \
doesn't give us long<br> >>> to bounce around ideas, but here are a few \
I was thinking:<br> >>><br>
>>> - There have been recent discussions between Jeremias, myself and<br>
>>> others about extracting the Fonts packages into their own library. I<br>
>>> think this would be a great idea for a project because essentially \
it<br> >>> only involves a few, well defined specifications (TTF, Type1 etc) \
and<br> >>> doesn't expose the person to too much complexity. The way \
I'd suggest<br> >>> this to be done, is by re-writing rather than \
porting, that way it<br> >>> gives the person much more flexibility and also \
the current code would<br> >>> give them good tips and tricks on how to deal \
with parsing fonts.<br> >>><br>
>>> - TTF in AFP. I know we still have the TrueTypeInPostScript branch<br>
>>> flying around, and however much I'd like to fob that onto \
someone<br> >>> else, I don't think it's fair to do so. I have no \
idea how long this<br> >>> project would take, but I think FOP could really \
benefit from it.<br> >>> Currently we're forcing users to use AFP fonts \
for AFP documents, a<br> >>> lot of which are archaic and use EBCDIC, for \
those of you who haven't<br> >>> been exposed to EBCDIC, count yourself \
lucky.<br> >>><br>
>>> There may be something to do with PCL?? I'm not at all familiar \
with<br> >>> the format, but I do remember discussions about upgrading to a \
newer<br> >>> PCL standard? I'd be happy to acquaint myself with the \
format if<br> >>> there's interest in the idea.<br>
>>><br>
>>> Hopefully we can get a proposal together in time.<br>
>>><br>
>>> Mehdi<br>
>><br>
>><br>
</div></div></blockquote></div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic