break Haml and Sass into separate projects

4 views
Skip to first unread message

Norman Clarke

unread,
Feb 1, 2010, 12:56:17 PM2/1/10
to haml...@googlegroups.com
Hi Nathan/Hampton/Chris,

I just read Nathan's blog post on the changes coming to Sass
(http://nex-3.com/posts/91-sass-2-4-will-now-be-sass-3-0) and I was
wondering if you guys have any thoughts about breaking Sass and Haml
into separate projects? It seems each one has grown up so much that
having them in one repository with the same versioning is beginning to
feel very forced; bumping Haml to 3.0 because Sass had many changes is
going to make the Haml version bump almost completely meaningless.

Personally I think if you have to mention in the README that you want
people to put [Haml] or [Sass] in their commit messages to make the
logs easier to read, it's an indication that it's already time to
split things up. As someone who uses Sass and Haml but only hacks on
the Haml source code, I would personally like to be able to check them
out separately.

If it's a matter of time/energy/effort I'm more than happy to help do
it. Since you're going to do a new major release, now might be a good
time to make this change.

Regards,

Norman

Norman Clarke

unread,
Feb 1, 2010, 1:02:59 PM2/1/10
to haml...@googlegroups.com
And sorry if I'm opening a can of project-internal worms. :-) Really
I've just been wondering about this for a while and wanted to register
my vote in favor of a velvet divorce, in the event that has any
import.

Nathan Weizenbaum

unread,
Feb 1, 2010, 3:11:05 PM2/1/10
to haml...@googlegroups.com
At some point, we will end up separating Sass and Haml. The problem with doing so immediately is that it would require a lot of effort that would be better spent getting Sass 3 out the door. Moreover, a lot of that work would be a lot easier for me to do; it has to do with infrastructure that runs on my server, pushing out the haml-edge gem and generating the website and so forth. There are probably a healthy amount of things we aren't considering, as well.

If you want to give it a try, go for it; it's all open-source. But it'll probably be difficult.

If you do do it, make sure to create the Sass repository by forking the existing Haml repository.

- Nathan

--
You received this message because you are subscribed to the Google Groups "Haml Dev" group.
To post to this group, send email to haml...@googlegroups.com.
To unsubscribe from this group, send email to haml-dev+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml-dev?hl=en.


Norman Clarke

unread,
Feb 1, 2010, 3:48:08 PM2/1/10
to haml...@googlegroups.com
Makes sense - I'll look into it some more after 3.0 gets out the door.

Chris Eppstein

unread,
Feb 1, 2010, 3:57:52 PM2/1/10
to haml...@googlegroups.com
I might take a pass at it once compass 0.10 is out the door.
Reply all
Reply to author
Forward
0 new messages