Make fest-api more discussion worthy

[paranoidsp]

As I see it , the primary aim is to get the fest-api to be able to host discussions not that different from github issues. I suggest we immediately get it to a point where we can start having bug reports from the users of the fest-api in the fest-api itself, and provide the functionality to discuss and close them .
Basically, get a start on the tasks and task discussion framework, along with improving the present commenting system and notifications.
What say?

[AbdealiLoKo]

The point of this was to not have task and task discussion frameworks.
On Apr 13, 2014 4:47 AM, "Karthikeya Viswanath" notifications@github.com
wrote:

As I see it , the primary aim is to get the fest-api to be able to host
discussions not that different from github issues. I suggest we immediately
get it to a point where we can start having bug reports from the users of
the fest-api in the fest-api itself, and provide the functionality to
discuss and close them .
Basically, get a start on the tasks and task discussion framework, along
with improving the present commenting system and notifications.
What say?

Reply to this email directly or view it on GitHubhttps://github.com//issues/33
.

[paranoidsp]

Point of what? What service will the fest-api provide, then?
On Apr 13, 2014 7:27 AM, "AbdealiJK" notifications@github.com wrote:

The point of this was to not have task and task discussion frameworks.
On Apr 13, 2014 4:47 AM, "Karthikeya Viswanath" notifications@github.com
wrote:

As I see it , the primary aim is to get the fest-api to be able to host
discussions not that different from github issues. I suggest we
immediately
get it to a point where we can start having bug reports from the users of
the fest-api in the fest-api itself, and provide the functionality to
discuss and close them .
Basically, get a start on the tasks and task discussion framework, along
with improving the present commenting system and notifications.
What say?

Reply to this email directly or view it on GitHub<
https://github.com/The-WebOps-Club/fest-api/issues/33>
.

Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-40297420
.

[AbdealiLoKo]

A communication platform
A file storage platform
And automation of tasks via portals

[paranoidsp]

On Apr 13, 2014 9:46 AM, "AbdealiJK" notifications@github.com wrote:

A communication platform
A file storage platform
And automation of tasks via portals
There you go.
Also generic tasks. Which is why a task framework.

Reply to this email directly or view it on GitHub.

[AbdealiLoKo]

By automation of tasks i meant stuff like "uploading spons logo on site", "event writeup on site", etc

Not a issue based task management system

[paranoidsp]

Why not? Other departments don't really have a ready tool like Github to
track their tasks. It's definitely one of the requirements from a generic
user perspective
On Apr 13, 2014 4:00 PM, "AbdealiJK" notifications@github.com wrote:

By automation of tasks i meant stuff like "uploading spons logo on site",
"event writeup on site", etc

Not a issue based task management system

Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-40304315
.

[AbdealiLoKo]

It will take time to make.
It was done for the last 2 yrs and never used.
If they want task allotment, infinite tools like git, trello etc are
available.
Above points => It is not priority.
The database is itself taking so much time. This is not priority at all ...

On Sun, Apr 13, 2014 at 5:06 PM, Karthikeya Viswanath <
notifications@github.com> wrote:

Why not? Other departments don't really have a ready tool like Github to
track their tasks. It's definitely one of the requirements from a generic
user perspective
On Apr 13, 2014 4:00 PM, "AbdealiJK" notifications@github.com wrote:

By automation of tasks i meant stuff like "uploading spons logo on site",
"event writeup on site", etc

Not a issue based task management system

Reply to this email directly or view it on GitHub<
#33 (comment)

.

Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-40305461
.

[srmanikandasriram]

I agree with Ali on this. What junta want is an intuitive communication platform. Which can be used for discussions. To have a balance, we can provide the functionality of users to pin certain posts - like having starred emails. This provides a way for them to track work while maintaining the merits of the FB based UI

[paranoidsp]

A tasks platform doesn't need to be a separate framework. Just having a few
more fields in a generic comment object should do it. Its not a great
undertaking in any sense, and something I think should be available , at
least at a rudimentary scale in the fest-api.
Asking the coords to use two different tools to work will be a losing
prospect, IMHO. It doesn't seem to be that big an undertaking from our
part, and don't forget that adding it now will be much easier than doing it
later when the api is more solid. If this is a project we don't want to
repeat and come back to again and again, we need to anticipate future
requirements too, rather than pandering to short term compromises.
Tl:Dr I think this is an easy to build feature that will see great use if
it is simple enough, and won't hurt us any doing it. We cannot afford to
give the fests something that lacks functionality, its what we promised
them won't happen.
On Apr 13, 2014 9:18 PM, "S.R.Manikandasriram" notifications@github.com
wrote:

I agree with Ali on this. What junta want is an intuitive communication
platform. Which can be used for discussions. To have a balance, we can
provide the functionality of users to pin certain posts - like having
starred emails. This provides a way for them to track work while
maintaining the merits of the FB based UI

Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-40310794
.