RFC#4: Areas of Responsibility

[daviddyess]

This RFC is for us to self identify our area(s) of responsibility. This is the piece or pieces of the project you intend and have the availability to contribute the most.

The individuals taking responsibility for specific facets of the project will take into account the input provided by the entire team and decide the best approach to satisfy that particular need. What this does is relieves some pressure on us and our seemingly unanimous desire to go along with what the team wants.

Involvement so far has been beyond my expectations, but for this to work we have to stay engaged and remember it's not as important what we each want, it's more important what we are providing to the community. It is most important for us to competently execute our desired goals. This could just be the first version and I've found over time projects evolve fairly differently from how they started.

Facets to consider and accept responsibility:

1) Web Site - Backend scripting; Backend database; Frontend Design; Frontend HTML; Frontend Scripting; Frontend CSS; Frontend Graphics; Testing; Other; All

2) Open API - Scripting; Database; Interfaces; Testing; Other; All

3) Hosting - Requirements; Budgeting; Providers; Strategy; Deployment; Sustainment

4) Community - Libraries; Example Uses;

5) Other - Quality Assurance; Public Relations;

6) Internationalization - i18n Locale Support

Please identify your areas of responsibility and we'll record them in the Wiki for reference. If I left something off or didn't identify something to the level you wish to contribute, please identify that as well.

Keep in mind, we are not dividing into groups, we are one group that is relying on eachother to maintain open communication and make sound decisions for the benefit of the community.

Once we have identified these roles, we will be able to assign issues on the tracker to individuals taking responsibility for those types of actions/concerns and allow us to more effectively know what is needed of us.

[pscn]

I see myself on the backend side of things, be it web site or API. Although I'm not to sure how much I can initially contribute depending on the language we choose (no node.js experience and my PHP knowledge dates back to PHP 3/4). But I usually find my way around existing code quickly and adding new features based on a blue brint, should be no problem.

I'm also willing to discuss DDL, but that also depends on what we choose. I work with Oracle in the office and played around with SQLite and MySQL in my free time. I wouldn't expect too much difficulty with PostgreSQL, but have zero experience with MongoDB.

I can also test deployment instructions and do manual front end tests (pasteing bullshit into UIs is so much fun :)).

If 4 includes writing libraries that use the API, I might give that a go (pun intended :)).

Another thing that I'd like to add to the scope would be internationalization. It would be cool if the front end would be prepared for that. I'm willing to add translations for German.

I was thinking about how much time I'm able to spend on this and my pessimistic assumption for the near future would be ~2-4h a week for programming. Discussion probably more.

So:

1 Web Site - Backend scripting; Backend database; Manual Testing 2 Open API - Scripting; Database; Interfaces; Testing 4 Community - Libraries; Example Uses;

[Korlimann]

Frontend seems like my kind of thing, at least, that's what I like doing and probably one of the things I did more often than to others.

I'd also be very interested in the Hosting point - and I think my friend could help me out a fair bit with that, I can probably work together with him on this, since he appears to be very interested as well.

Also, I'm not to sure what Quality Assurance would actually consist of, but if I understood Public Relations correctly, I could do that, since I already contacted DIYorDIE anyway, as well as writing the initial post on the subreddit.

So:

1. Website - Frontend Design; Frontend HTML; Frontend Scripting; Frontend CSS; Frontend Graphics
2. Hosting - Requirements; Budgeting; Providers; Strategy; Deployment; Sustainment
3. Other - Public Relations

[daviddyess]

Added i18n, good catch @pscn and Yes, 4) is for libraries and tools that help others use the API :)

My main interest is in the API and that is what I plan to focus on the most. I will offer marathon coding sessions to contribute anywhere that needs attention, but I'm not as concerned how we implement the web site. I just ask that we consider cost, as we do not yet have a funding strategy.

[Caedis]

I can spend my some of my free time working on:

1 Web Site - Backend scripting; Backend database; Manual Testing 2 Open API - Scripting; Database; Interfaces; Testing 4 Community - Libraries; Example Uses;

[nickdurcholz]

I'm very interested in this project and could contribute to anything on the backend, api, hosting / deployment, or even QA fronts. However, my availability is limited

[Korlimann]

Thanks a lot @nickdurcholz for offering your help, we highly appreciate your help :) If you'd like you can join our current Discord Group here

[ayan4m1]

I can provide assistance with the back and front end development tasks - architecture, data model, interface and implementation. I can also provide assistance with the ops side of things - server setup and administration. I don't want to overextend myself though, so hopefully there will be others in both of those camps.

1. Site - Any
2. API - Any
3. Hosting - Strategy, deployment

[mckernanin]

I'd be happy to help take the lead on the front end side of things. My background is running teams of front end devs at agencies, having switched over to a product company in the past year. I'm not a designer but can get something decent together (place for something like this to start is a UI framework tbh, material, bootstrap etc). Been working in node on apis for the last 2 years, some older experience in PHP (but nothing I'm proud of). Happy to help on backend side as well where I can.

1. Web Site - All, including automated testing

[beleniak]

Design/ implementation/optimization.

I am most useful on the backend. Business logic, Database, Interfaces (read API).

I can assist on the front-end, but I have been out of the loop there for yarons, so just ignore me if I start giving too much technical advice in that area ;)

[JosefBud]

I'm a little late, just doing my monthly /r/diy_ejuice lookaround, but if you still need help with it, I can try to help with

1. Web Site - Frontend HTML; Frontend Scripting; Frontend CSS