Skip to content
This repository has been archived by the owner on Apr 2, 2019. It is now read-only.

[Extra Maintainer(s) Wanted] #244

Open
wyuenho opened this issue Jun 21, 2013 · 19 comments
Open

[Extra Maintainer(s) Wanted] #244

wyuenho opened this issue Jun 21, 2013 · 19 comments

Comments

@wyuenho
Copy link
Contributor

wyuenho commented Jun 21, 2013

Ever since the first version of Backgrid was released in January, the project has become really popular and yet at the same time I have less time available dedicated to it as I would have liked.

I'd like to get a new release out every 2 weeks to a month until 1.0.

I'd like to improve the build process and performance.

I'd like to get more crucial features done faster and better.

I'd like to be able to roll out a fix for every bug discovered within 48 hours.

I also would like to have a free weekend once in a while without stalling progress.

Here's what I propose:

  1. You give at least a couple of hours a week to help answer questions, propose solutions, file tickets and pull requests.
  2. I offer guidance along the way until I trust you enough to give you direct write access to the repository.
  3. Put your name, and/or project, and/or product, and/or company up for notice prominently.

What you should NOT worry about:

  1. Not good enough, because no one ever is.
  2. Have lots of questions. I'm pretty responsive unless I'm sleeping. I usually sleep at around 1am (GMT +8). My goal is to answer all your questions as quickly as possible until you run out of them, so you can start making decisions.
  3. On a Windows machine. Because you'll be helping me to move the documentation and build process over to Grunt.

What you will get:

  1. Understand Backbone and Backgrid better.
  2. Experience.
  3. Something awesome to put on your resume.
  4. Fame.
  5. Give something back to the community.
  6. Profit (probably).

Let me know if anyone is interested.

@mallim
Copy link
Contributor

mallim commented Jun 21, 2013

Hi wyuenho

I am not very familiar with Backgrid but got decent experience with grunt and backbone.

What kind of help do u need for the documentation and build process on Grunt?

Regards
Ian Lim

@wyuenho
Copy link
Contributor Author

wyuenho commented Jun 21, 2013

@mallim See #24, #25, #79, #84, #165 and #236.

Comment on the tickets if you have more questions.

@morficus
Copy link
Contributor

morficus commented Jul 5, 2013

Hey @wyuenho,
Similar to mallim, I'm not super familiar with Backgrid (yet) but I do have a lot of experience with Backbone.
Any particular feature for 0.3 or 0.4 you would rather I look at first?

@wyuenho
Copy link
Contributor Author

wyuenho commented Jul 5, 2013

Hi @morficus! Thanks for lending a helping hand! I think if you want to get familiar with Backgrid, #210, #247 and #258 will be the easiest way to get started. Let me know if you have any questions. Just dive in the code and submit PRs, I'll help you out along the way.

BTW, @mallim can you send me an email?

@bruno-c
Copy link
Collaborator

bruno-c commented Jul 29, 2013

Hey @wyuenho, I've been using Backgrid in our application pretty much since it came out and I feel I know it quite well. If you still need some help with the project, feel free to contact me here or email: neonskimmer@gmail.com

@tgriesser
Copy link

@wyuenho so I'm actually using Backgrid a bit as the foundation of a functional reactive form builder... kind of neat, hoping to get to open source it at some point, but I could be interested in helping out a bit here and there. I've had a few ideas about this and related libs (the other tickets I had about the templates, de-coupling paginator UI from requiring a pageable collection for instance) and I know that it's always good to have people helping out with things :)

@wyuenho
Copy link
Contributor Author

wyuenho commented Nov 11, 2013

@tgriesser Damn you are way ahead of me, I had been thinking about extracting those cell classes so people can use them to build forms.

Thanks for reaching out! I'm in the middle of restructuring the docs and building a Backgrid bundler for people who want to customise their builds but too busy to deal with npm and grunt.

It would be great if folks here would help me out with the PRs for the extensions in the other repos. Just commenting on them and/or writing tests for them would be great help :)

@tgriesser
Copy link

I'm in the middle of restructuring the docs and building a Backgrid bundler for people who want to customise their builds but too busy to deal with npm and grunt.

Had you considered better support for AMD? After finally using it a bit with Knex & Bookshelf (hoping to eventually get those working outside of node, with say a web/mobile sqlite3 db) it's actually not as bad as Jeremy claims it is ;) ... there's just IMO way too many options in the require API to the point that there's like 20 different ways to do the same thing, which can be a bit confusing and lead to doing things incorrectly... but when used properly it can lead to modular code which is easier for folks to extend & custom build without hacks.

@wyuenho
Copy link
Contributor Author

wyuenho commented Nov 11, 2013

Supporting it is easy. Just need to put in an extra if block in the UMD header in the Grunt file for core and all of the extensions. There's no point fighting it now I guess. If AMD gets obsoleted by ES6 in a couple of years, great, if not, no one can blame us.

@tgriesser
Copy link

Wouldn't putting it in the grunt file as opposed to the individual files sort of defeat the purpose though?

@wyuenho
Copy link
Contributor Author

wyuenho commented Nov 11, 2013

The core should be one giant inseparable unit for now. Most of the classes make no sense to be separately importable anyway. I'd take my module pattern anyday over a bunch of UMD everywhere. Most of the core Cell classes are so small, the UMD block has more code than the meat.

@tgriesser
Copy link

Most of the classes make no sense to be separately importable anyway.

Well, if they could be easily modified as modules then it'd be much easier to replace individual modules before assembly rather than create and maintain a hacked up full version of it locally as I'm doing now... just sayin'

@wyuenho
Copy link
Contributor Author

wyuenho commented Nov 11, 2013

How hacked up is it?

@tgriesser
Copy link

Pretty hacked up. A bunch of instanceof checks needed to go because I'm not actually using the copy of Backbone that your app assumes when it checks instanceof Backbone.Collection and some other things very specific like that.

@marti1125
Copy link

I would like to help :)

@wyuenho
Copy link
Contributor Author

wyuenho commented Dec 10, 2013

Would be nice if you could help me port the text cell extension over to bootstrap 3 :)

@marti1125
Copy link

yes :),
I just a problem with this
name: "amount",
label: "Amount",
editable: false,
cell: Backgrid.Cell.extend({ render: function (
this.$el.html('Total Amount ('+ this.model.attributes['amount'] +')');

});
how to change value using this model.set({amount: 5});

@wyuenho
Copy link
Contributor Author

wyuenho commented Dec 10, 2013

Rerendering is automatic and it's already done for you by the cell's constructor, but as you can see from the syntax highlighting, your string is wrong and you probably want to use this.mode.get(this.column.get("name")). See Backgrid's source code for details.

@marti1125
Copy link

have a look https://gist.github.com/marti1125/7885287

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

No branches or pull requests

6 participants