Progress / Roadmap #557
Comments
|
I'm also curious. This project seems to be a really good alternative. Although BS has a huge community already, this is a big advantage. |
|
There will be new maintenership news in April and things will start moving again. |
|
:) Cool! Thanks. |
|
@lkraav 👍 |
|
Cool. Good job by the way. |
|
good to hear! |
|
👍 On 9 March 2016 at 17:04, krebbi notifications@github.com wrote:
|
|
Good job~~ |
|
Keep up the great work, thank you. |
|
I are glad to know the good news. |
|
Great things shouldn't stop. I am very happy to know this news. Keep going 👍 |
|
Thanks. All of the support means a lot. |
|
👍 |
|
The project lives! Yes!! I find this to be one of the best/easiest to wrap into the projects I touch that have pre-existing, and "untouchable", css. Can't wait to see where it goes next! |
|
I love purecss, because it is fat free. Thanks a lot for keeping it alive! |
|
I was looking at possibly using pure for my next app and wondering this very thing. Still a little nervous considering the last release was over a year ago but I'm glad good news is coming. |
What I could do is push a small experimental update to |
|
Any update on the new maintenership? |
|
Thanks for the update @redonkulus |
|
looking forward to it! |
|
Would love to hear more! |
|
any news? |
|
Any news on this @redonkulus @lkraav ... perhaps a concrete and reliable road map, so people know what to expect from Pure in the near future. |
|
@michel-tournier for me, several big life events have held this transition up (big projects completions, new baby, moving to a bigger place etc). At the same time, poking @redonkulus for updates is the most that the current state of infrastructures would have allowed me to do, regardless of my availability. I am not sure if the infrastructure transition planning meeting has been held at yahoo yet. @redonkulus can you provide any insight into the current state of things on your end? |
|
@lkraav that explains a lot, thanks. And congratulations on those big life events! |
|
@lkraav We are currently close to launching a couple of big projects as well at Yahoo. Once those are done (a couple of weeks if the dates hold) I will be able to focus on Pure and work on the transition plan. So hopefully in June, we can sync up and do a proper hand off. My apologies to the community for taking so much time on this. We appreciate your support and patience. |
|
Sorry, didn't see this before. I would have to defer to @gyehuda for the licensing questions relating to Yahoo/Verizon. |
|
@redonkulus I think your answers above in the thread are correct. The eventual separation of altaba from yahoo "core" and the sale of the latter to Verizon is a business transaction that we expect to have almost no effect on our open source projects. Basically Yahoo employees will have a different signature on their (our) paychecks. We still plan to do what we do in the open source space because we believe its the best way to manage and develop these kinds of technologies. There are times when we gladly transfer projects from our governance to the governance of a community -- usually a foundation. If the PureCSS community wants this, if it makes sense to the folks involved, I'm glad to do that. There's some paperwork, and I'll process it. Let's do it when it makes sense (and if there's a good destination), but not our of fear of the unknown. If the website is not already open source, we can make that open source too (so that if tomorrow we vaporize, the community could regenerate a new website by simply registering a new domain and uploading the code). |
|
Any progress / updates @redonkulus @gyehuda @lkraav ? |
|
@michel-tournier what would you like to see happen next? I'm sorry but I'm not sure what the specific "ask" is now. What would you like to do? how can I help enable that? |
|
@gyehuda it seems to me that you guys have no plans whatsoever to keep pureCSS alive. More than 2,5 years have passed without any progress at all. A concrete and reliable road map, so people know what to expect from Pure in the future, doesn't exist. Many promises were made that were not fulfilled. Like @KrisSiegel correctly said back in November 2016: there is a lot of chatter back and forth, but in reality nothing happened. pureCSS was a great framework with a lot of potential. It had an active, passionate community relying on it, and wanting the project succeed and thrive. Such a shame. |
|
@michel-tournier you are correct in your assessment. There is no active team assigned to maintain and manage Pure. Anything done in the past few months has been done via free time. If you or anyone else wants to take over and maintain Pure we would certainly be accommodating, as I've said in the past. |
|
From my perspective there are two "community" components, there are consumers and there are maintainers. PureCSS does not have maintainers, that is not anyone's fault. Nobody has stepped up to help maintain the project. I still use PureCSS myself and I consider it feature complete. Yahoo has made it clear they will not be dedicating resources to this project like they used to. It is no longer used by them and their internal team that wrote the initial releases has disbanded. Yahoo has basically said they will turn over ownership of this project to anyone who wants it but nobody with any amount of free time has stepped up. Unless you have actionable and productive inputs to move the project forward, bumping this thread isn't going to help. I suggest we meet in IRC or slack or something and gauge peoples actual interests. Maybe we can come up with some actionable work and split up tasks among volunteers. IRC I'm in |
|
A couple of months ago I decided for myself that Pure is very unlikely to be developed further anymore so I should look for an alternative that is similar to Pure, but using more modern techniques like flexbox etc. Failing to find one that suits me I've decided to go ahead and do something myself, which would allow me to make it very similar to Pure and thus - an easy update for older sites that I'm maintaining. So I've come up with https://github.com/talkingaboutthis/tat-css and this is what I'm already using on any sites I built. Take a look if it would work for any of you. It works very similar to Pure for regular grids, but in flexbox and thus allowing all other awesome flexbox features. So any site done with pure can be converted by just changing the css class prefix from pure to tat, while for newly built sites there are many more features. |
|
Going to close this as it is not roadmap related anymore. We can continue discussion if need be. |
|
Hmm, I didn't see anything resolved here. Did someone pick up the maintenance for this project and if so what's the roadmap? |
|
I've professed my love for this framework countless times, here (see above) and to colleagues. I would love nothing more than to be "the person" or one of the people that takes this over. In fact I've gone as far as to clone the repo several times, only to stop because I find it more complicated than I believe necessary, for example why do we even need grunt? Wouldn't a SASS or LESS mixin to generate the grid do?. This is why I've written my own "version" of pure called Hydrogen for this very reason. Please note that this isn't a self solicitation, by no means am I encouraging using my interpretation over Pure. I simply say all of this as a means of making a point in hopes that someone helps me understand. If anyone here is interested in pursuing an offshoot/takeover of Pure with me, based on a SASS/LESS model. Please let me know. |
|
@pimbrouwers |
|
In addition to that, if anyone wants to join me in maintain Hydrogen and ensuring its coverage matches Pure, I am also happy to collaborate in that fashion! |
|
@gyehuda wow, crazy timing. I think we submitted almost simultaneously there.... That makes sense to me! However, I want to be clear that Hydrogen is not a fork. It's a ground up re-interpretation, with almost full coverage of Pure's features. That said, I'm happy to have people join me on the journey of carrying this "style" of framework forward. |
|
Let's get a few +1s from people before changing this, or at least give people a day to speak up if this is not good for someone. @redonkulus -- are you OK with this? |
|
@gyehuda do we really need to fork? Couldn't @pimbrouwers just be added as a collaborator to this repo (plus other Pure repo's) and do the work here? I'd prefer to not to fork and fragment the community. I'm fine with removing the Grunt stuff to make it easier to maintain and contribute. Thoughts? |
|
@redonkulus @gyehuda I'm happy with either. Just want to say again that mine isn't an explicit fork. Just an attempt to match the surface area of Pure. That said, I am more than happy to migrate the project into this repo. Obviously first as new branch, and once approved, into the master. |
|
@pimbrouwers I'm glad to add you as a collaborator to this repo. I understand that forking might cause confusion in the community, so it's perfectly ok to keep the code here. You are welcome to bring in the best work from the community and help run this project on our behalf for as long as this makes sense. At the end of the day we want this code to live and do the best it can for those who want to use it. Bring realistic, we are not investing our own people on this project. So it's really up to the community. If we every feel the need to move the code, you can (it's open source) and if you need help with github permission things, let me know. |
|
Given that Yahoo is not interested in being stewards of this project and its community, the best thing that can be done IMO is to move this codebase to a new "Pure" organisation where it can be run by the community itself. So the repo URL would change from github.com/yahoo/pure to github.com/pure/pure The relevant docs on transferring a repo to a new organisation: |
|
Let me suggest opening a call to the community to determine the preferred venue for Pure going forward. It can stay here, or be transferred to a different location. @redonkulus you are an owner and can execute the transfer if need be. |
|
@pimbrouwers I procured the |
|
I was considering offering to take over the project. I'd like to also offer to take over this project as well and see that PureCSS continues to improve and be maintained. As far as @pimbrouwers's project... I would personally prefer to keep those separate. Mostly because they're separate things, as noted by pimbrouwer. I don't think it'd be a good idea to merge the two projects as they're designed to do different things with same goals. |
@redonkulus I am down for that. I accepted my previous invite into the yahoo repo. I left because the two-factor auth became a hassle. So my only request would be that the p.s. sorry for the delay, been away for holiday's |
|
Sorry for the delay. The holidays slowed things down for me but I’m getting back in the swing of things. To resolve this and ensure the project get the attention it needs, I would like to do the following:
If this sounds good, I will get started. |
|
Sounds good to me! |
|
I'm going to close this task as I created a new one to follow the items needed to complete the transfer. If anyone from this thread is interested in following along, please subscribe to the following issue: #691 |
and others
I'm just curious about the current state and the maintenance of this project as the oldest issue is from 3rd of july 2013 with actually 85 open issues and 20 open pull requests - where the oldest ist from 23rd july 2013.
is this project still relevant or did you guys give up against bootstrap?
The text was updated successfully, but these errors were encountered: