Anyone willing to give this repository some love?

[igorsantos07]

Hey guys!

There's a long time since the original maintainer of TurbineCSS have abandoned the project. Since then, as I was a big user of the system, I talked to him and moved stuff to my ownership, maintaining the doc website alive and the repository open.

However, I haven't been using the project for some time now, and never had time to really take care of the code and improve it - first because I never got my hands dirty in its source code to feel free to mess around, and second because I never had free time for that.

So I was cleaning my files and stuff in the computer and found the project website there, and came here to see how stuff is. There's a couple of PRs taking dust and issues around there... And I would like to know if there's anyone willing to enter the team and work in the main repository, accepting PRs and stuff.

Calling people with forks that had some activity!
@commi, @MattiSG, @digilist, @ibolmo, @brinley, @jaakon, @srounce, @derpixler

[ibolmo]

No longer using the project. Sorry! :)

[srounce]

I'm afraid I'm no longer using this project, it was used by legacy code at a former job.

Best wishes in your search for a new maintainer!

On 10 Jun 2013, at 12:11, Igor Santos notifications@github.com wrote:

Hey guys!

There's a long time since the original maintainer of TurbineCSS have abandoned the project. Since then, as I was a big user of the system, I talked to him and moved stuff to my ownership, maintaining the doc website alive and the repository open.

However, I haven't been using the project for some time now, and never had time to really take care of the code and improve it - first because I never got my hands dirty in its source code to feel free to mess around, and second because I never had free time for that.

So I was cleaning my files and stuff in the computer and found the project website there, and came here to see how stuff is. There's a couple of PRs taking dust and issues around there... And I would like to know if there's anyone willing to enter the team and work in the main repository, accepting PRs and stuff.

Calling people with forks that had some activity!
@commi, @MattiSG, @digilist, @ibolmo, @brinley, @jaakon, @srounce, @derpixler

—
Reply to this email directly or view it on GitHub.

[brinley]

Hi,

I am still actively using this project. However, I do not have time to take
over the project entirely but I am happy to assist with reviewing and
approving any PRs occasionally when I get some free time.
Thanks

Regards,
Brinley

[commi]

Hi,

is still use Turbine in a couple projects (since i find LESS/SASS still
lacking higher functionality sometimes) if would like to keep it updated
with new CSS3 features and such.

Since I go through the source now and then to hunt bugs i could accept
patches, but i dont have time to maintain a "neutral" main repo. Maening I
would work in bug fixes and enhancements that i personally would find worth
it. For example i would work on any IE6 specific stuff, since that is not
worth the effort anymore, even if Turbine was once also created with old
IE's in mind:)

Greetings,
-Till

[igorsantos07]

Yeah, that's fine (:

I'm happy for maintaining the structure behind the project, but once I've
migrated to LESS and I'm hardly going back. However, I do agree that the
project has its reasons and don't want it to die, so any help is awesome (:

I'll add you as a collaborator soon.

If you feel the need to update the website, the repository is there as
well. I'll subscribe to its feed so I can deploy new versions when needed.
On Jun 11, 2013 4:50 AM, "commi" notifications@github.com wrote:

Hi,

is still use Turbine in a couple projects (since i find LESS/SASS still
lacking higher functionality sometimes) if would like to keep it updated
with new CSS3 features and such.

Since I go through the source now and then to hunt bugs i could accept
patches, but i dont have time to maintain a "neutral" main repo. Maening I
would work in bug fixes and enhancements that i personally would find
worth
it. For example i would work on any IE6 specific stuff, since that is not
worth the effort anymore, even if Turbine was once also created with old
IE's in mind:)

Greetings,
-Till

2013/6/10 Igor Santos notifications@github.com

Hey guys!

There's a long time since the original maintainer of TurbineCSS have
abandoned the project. Since then, as I was a big user of the system, I
talked to him and moved stuff to my ownership, maintaining the doc
website
alive and the repository open.

However, I haven't been using the project for some time now, and never
had
time to really take care of the code and improve it - first because I
never
got my hands dirty in its source code to feel free to mess around, and
second because I never had free time for that.

So I was cleaning my files and stuff in the computer and found the
project
website there, and came here to see how stuff is. There's a couple of
PRs
taking dust and issues around there... And I would like to know if
there's
anyone willing to enter the team and work in the main repository,
accepting
PRs and stuff.

Calling people with forks that had some activity!
@commi https://github.com/commi, @MattiSG https://github.com/MattiSG,

@digilist https://github.com/digilist, @ibolmo<
https://github.com/ibolmo>,
@brinley https://github.com/brinley, @jaakon <
https://github.com/jaakon>,
@srounce https://github.com/srounce, @derpixler<
https://github.com/derpixler>

—
Reply to this email directly or view it on GitHub<
https://github.com/TurbineCSS/Turbine/issues/182>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/182#issuecomment-19247408
.

[commi]

Great:)

[MattiSG]

Hi there,

I'm afraid I won't have enough time to spend on a project I'm not using anymore. I still think Turbine's approach to CSS is far superior to LESS/SASS etc, mostly thanks to its built-in vendor-expansion and per-client caching.

Though, I haven't been working with PHP for almost 2 years now, and the project that was using it is not in active development anymore. I might go back to it in a few months from now, in which case I'll definitely chime back in.

Best of luck with maintaining that repo, and don't hesitate to call again if a serious need emerges.

Regards,
Matti