Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2015 Revamp? #345

Open
zvikazend opened this issue Jan 18, 2015 · 3 comments
Open

2015 Revamp? #345

zvikazend opened this issue Jan 18, 2015 · 3 comments
Labels

Comments

@zvikazend
Copy link

The project seems to die slowly, and there is no reason to!
The domain is great, the updates are public, and I believe the only problem kicking ass here is the indexing.

Some columns can be used to make this box list useful (again):

  1. Tags (for example, to mark a box unmaintained or archived)
  2. Updated (latest boxes?)
  3. OS Family (Linux / Windows / BSD-Unix / ChromeOS / OS X / Android-x86 / Other)

My proposed action is to start a 2015 index and drop all other boxes into archive.

@JonTheNiceGuy
Copy link
Collaborator

Firstly, let me clarify this by saying that these views are my own, not those of the Vagrantbox.es project.

So, I can see some benefits to the tags (but not in the way you've proposed it) and the OS Family. We currently don't do any polling of images, so it makes it hard to see when a box is updated, unless someone submits a new PR we won't see when a box is archived or updated.

Adding tags like "puppet", "chef", "vanilla" and things like that could be useful (they're currently tracked in the image name column), and having the OS explicitly tracked would, again, make it easy to search.

I'd be reluctant to "drop" anything though, as that would devalue the list considerably.

@garethr any thoughts?

@garethr
Copy link
Owner

garethr commented Jan 19, 2015

Hi @JonTheNiceGuy. I guess in reality I just don't have much time to commit to this project unfortunately.

I'd be interested in seeing some of it happen, but the current setup (flat files auto-publishing to Heroku) only allows so much flexibility.

With that in mind I'd be happy to transfer the domain name if you're interested in taking a different approach, it sounds like a few other people would happily contribute too. The level of filtering and flexibility would likely benefit from some sort of web framework I'd guess, and you could seed it with the existing data from the current site.

Let me know if that's of interest. You've done a great job looking after it for the last year or so, I'd rather see you able to make whatever decisions you think are best/have time for rather than rely on me.

@JonTheNiceGuy
Copy link
Collaborator

@zvikazend I've not ignored this request, I'm just trying to work out how to engineer it!
@garethr I'll try and drop you an e-mail with some thoughts, and see what you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants