Since this project is abandoned, is there anyone who has thought of making a new fork to continue Adirelle's work?

If some people volunteer to maintain the project, I can add them to the wowace project some they could push new versions. I also accept push requests.

Adirelle, Has anyone volunteered to maintain this? I have never developed for wow but I have developed other addons in the the last few years and am willing to learn what I must to keep it going. I love adibags and didn't realize until it broke with this Legion pre-patch that it was on hold project.

thanks!
-Tania

Not that I am aware.

That said, if some people, like you, @Cidan or @Talyrius would like to co-maintain the addon, I could give you the permission to do so, both no wowace and here. I have already handed down the maintenance of AdiButtonAuras and LibDualSpec-1.0. I am still hanging around anyway.

I wouldn't mind helping around and making sure the add-on continues to work as intended; my changes wouldn't really be that major, just enough to make sure it works error free for as long as I play WoW.

It looks like there are many people like me who love adibags and are willing to help keep it going. I have some enhancement ideas of my own so I might contribute as time passes. co-maintain is good.

Yes, I'm willing to lend a hand.

You have been invited. I'll soon setup a system to push master and tags to wowace (and the curse client) from github.

Just a few guidelines:

• Please respect the coding style (soon to be enforced by a check):
  • indentation with tabs only,
  • alignment with spaces only,
  • no trailing space at end of lines,
  • variable names are camelCased whereas function and method names are CamelCased.
  • "long" variable names.
• Code the new features in dedicated branches, and merge them when they are almost finished. Ideally, I'd like someone else than the branch author reviewed the code.
• Beware of feature bloat: do not include every features asked bu the users. I already felt for this, which is what makes AdiBags quite complicated to maintain.

I don't particularly think (much) feature expansion should happen with the current iteration of AdiBags. At best, we should work to stabilize any issues that may appear. Once issues are stable and bugs are eliminated, we can take a real look at refactoring large sections of code and removing a lot of the complexity behind AdiBags.

Ideally, I'd like someone else than the branch author reviewed the code.

Heya. I haven't done any real work on AdiBags except for some small personal hacks, but if you need another set of eyes for reviewing changes, I'd be happy to help.

I have setup continuous integration with travis-ci. It mainly tests the syntax and the code styling for now. It also push working builds to wowace.

I have created a chat room on gitter. Its uses is not mandatory but it can be handy to discuss. You can use your github account.

I'm going to go ahead and close this to keep the issue log clear. Join us on Gitter!