Thread: [cssparser-developers] Plans for the Future

Hi Alan et al,

First off, thanks for letting me join the project. So... what's the plan
going forward?

There are a couple of tasks I'd like to tackle, let me know what you think
about each:

1. I'd like to convert the CVS repo to SVN [1]. However, I think you have to
be an admin to do this.
2. I'd like to convert the build system to Maven 2.
3. The build currently excludes DOM and SAC interfaces from the generated
JAR.
    a. I think DOM exclusion makes sense, but I'd like to just delete these
interfaces from the repo.
    b. I think SAC exclusion doesn't make sense, and I'd like to include
them in the generated JAR.
4. There aren't hardly any unit tests right now. I'd like to add some base
"sanity" unit tests and start to add unit tests for each bugfix.
5. Start fixing bugs!
6. Get a new release out very soon.

Again, let me know what you think of each of these.

Regards,

Daniel


PS: I think the mailing list is private or something, because it's not
visible when you go to http://sourceforge.net/mail/?group_id=82996 . Can you
make it public?


[1]
http://alexandria.wiki.sourceforge.net/Subversion+-+Version+Control+for+Source+Code#tocSubversion%20-%20Version%20Control%20for%20Source%20Code6

-- 
Daniel Gredler
http://daniel.gredler.net/

Comments inline:

On Tue, Mar 18, 2008 at 1:25 PM, Alan Krueger <al...@tr...> wrote:

> D&J Gredler wrote:
> > First off, thanks for letting me join the project. So... what's the
> > plan going forward?
> I'm somewhat new to the project myself, though an infusion of those with
> time and energy to contribute is a good thing, IMHO.
> > There are a couple of tasks I'd like to tackle, let me know what you
> > think about each:
> >
> > 1. I'd like to convert the CVS repo to SVN [1]. However, I think you
> > have to be an admin to do this.
> SourceForge supports Subversion now?  I'm happy to hear that.  I'm
> personally in favor of this, but I like to be sure the longer-term
> contributors to the project don't have any qualms about such a switch.


Are any of them on this list?

> > 2. I'd like to convert the build system to Maven 2.
> I'm not familiar with Maven, though I keep meaning to do a little
> research into it.  What would this do for us?


A standardized build lifecycle, automated dependency management, and easier
deployment of releases to the central maven repository. For example, right
now the ant script requires users to intall JavaCC and set a
corresponding environment variable. With Maven2, you configure the JavaCC
plugin to be used during the (standard) generate-sources build phase, and
the plugin and its dependencies are automatically downloaded as necessary.
No need for preconfiguration. Same with JUnit for the unit tests, which get
run during the (standard) test build phase.

> > 3. The build currently excludes DOM and SAC interfaces from the
> > generated JAR.
> >     a. I think DOM exclusion makes sense, but I'd like to just delete
> > these interfaces from the repo.
> >     b. I think SAC exclusion doesn't make sense, and I'd like to
> > include them in the generated JAR.
> I'll need to look at the code to see what you're referring to.


OK, let me know what you think.

> > 4. There aren't hardly any unit tests right now. I'd like to add some
> > base "sanity" unit tests and start to add unit tests for each bugfix.
> I'm very much in favor of unit and standards-compliance tests.


OK.

BTW, did you get a chance to make the mailing list public?

Regards,

Daniel


-- 
Daniel Gredler
http://daniel.gredler.net/

D&J Gredler wrote:
> Comments inline:
>
> On Tue, Mar 18, 2008 at 1:25 PM, Alan Krueger <al...@tr... 
> <mailto:al...@tr...>> wrote:
>
>     SourceForge supports Subversion now?  I'm happy to hear that.  I'm
>     personally in favor of this, but I like to be sure the longer-term
>     contributors to the project don't have any qualms about such a switch.
>
>  
> Are any of them on this list?
I mass-subscribed all current developers on the project to the list when 
I created it.

D&J Gredler wrote:
> BTW, did you get a chance to make the mailing list public?
The goal would be to limit the list to development members of the 
project.  The list is currently not public, but I'm unclear whether that 
helps meet that stated goal or not.

I think dev lists are usually public. Imagine, for example, that someone
wants to become active in the project. The natural progression would be to
read the mailing list archives, then subscribe and watch silently for a
while, then maybe start becoming active on the mailing list, submit some
patches, and then become a committer.

Would you rather keep it private? If so, how come?

Regards,

Daniel

On Wed, Mar 19, 2008 at 12:52 PM, Alan Krueger <al...@tr...> wrote:

> D&J Gredler wrote:
> > BTW, did you get a chance to make the mailing list public?
> The goal would be to limit the list to development members of the
> project.  The list is currently not public, but I'm unclear whether that
> helps meet that stated goal or not.
>
>
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>

-- 
Daniel Gredler
http://daniel.gredler.net/

D&J Gredler wrote:
> I think dev lists are usually public. Imagine, for example, that 
> someone wants to become active in the project. The natural progression 
> would be to read the mailing list archives, then subscribe and watch 
> silently for a while, then maybe start becoming active on the 
> mailing list, submit some patches, and then become a committer.
>  
> Would you rather keep it private? If so, how come?
Not really.  For some reason, I got it into my head that it should be.

I plead a long week already at work.  =)

Hi Daniel

D&J Gredler schrieb:
> 3. The build currently excludes DOM and SAC interfaces from the generated
> JAR.
>     a. I think DOM exclusion makes sense, but I'd like to just delete these
> interfaces from the repo.
>     b. I think SAC exclusion doesn't make sense, and I'd like to include
> them in the generated JAR.

I don't understand why excluding DOM makes sense whereas excluding SAC 
doesn't. The SAC API can be found at 
<http://www.w3.org/2002/06/sacjava-1.3.zip> available from 
<http://www.w3.org/Style/CSS/SAC/>.

> 5. Start fixing bugs!

And start by formally closing already fixed issues   :-)

Waldbaer

-- 
Johannes Koch
In te domine speravi; non confundar in aeternum.
                             (Te Deum, 4th cent.)

Hi Waldbaer!

I didn't realize that there was a SAC JAR published by the W3C. I'll try to
get it added to the central Maven repo.

As far as closing bugs that are already fixed, do you know which ones are
fixed?

Regards,

Daniel

On Wed, Mar 19, 2008 at 6:03 PM, Johannes Koch <ko...@w3...>
wrote:

> Hi Daniel
>
> D&J Gredler schrieb:
> > 3. The build currently excludes DOM and SAC interfaces from the
> generated
> > JAR.
> >     a. I think DOM exclusion makes sense, but I'd like to just delete
> these
> > interfaces from the repo.
> >     b. I think SAC exclusion doesn't make sense, and I'd like to include
> > them in the generated JAR.
>
> I don't understand why excluding DOM makes sense whereas excluding SAC
> doesn't. The SAC API can be found at
> <http://www.w3.org/2002/06/sacjava-1.3.zip> available from
> <http://www.w3.org/Style/CSS/SAC/>.
>
> > 5. Start fixing bugs!
>
> And start by formally closing already fixed issues   :-)
>
> Waldbaer
>
> --
> Johannes Koch
> In te domine speravi; non confundar in aeternum.
>                             (Te Deum, 4th cent.)
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Alan Krueger wrote:
> D&J Gredler wrote:
>   
>> I think dev lists are usually public. Imagine, for example, that 
>> someone wants to become active in the project. The natural progression 
>> would be to read the mailing list archives, then subscribe and watch 
>> silently for a while, then maybe start becoming active on the 
>> mailing list, submit some patches, and then become a committer.
>>  
>> Would you rather keep it private? If so, how come?
>>     
> Not really.  For some reason, I got it into my head that it should be.
>
> I plead a long week already at work.  =)
>   
It should be a public mailing list now.  New subscriptions also do not 
need approval.

- Alan

Cool, thanks Alan :-)



On Thu, Mar 20, 2008 at 11:47 AM, Alan Krueger <al...@tr...> wrote:

> Alan Krueger wrote:
>
> D&J Gredler wrote:
>
>
> I think dev lists are usually public. Imagine, for example, that
> someone wants to become active in the project. The natural progression
> would be to read the mailing list archives, then subscribe and watch
> silently for a while, then maybe start becoming active on the
> mailing list, submit some patches, and then become a committer.
>
> Would you rather keep it private? If so, how come?
>
>
> Not really.  For some reason, I got it into my head that it should be.
>
> I plead a long week already at work.  =)
>
>
> It should be a public mailing list now.  New subscriptions also do not
> need approval.
>
> - Alan
>



-- 
Daniel Gredler
http://daniel.gredler.net/