epall / oss_dashboard Goto Github PK

You may consider adding a small legend with a red block next to the description of red, a yellow block next to the description of yellow, etc, rather than just a text sentence at the top of the page.

Every week, email the RCOS group with a friendly update of activity on Dashboard

I attempted to link directly to an rss feed: http://www.natestedman.com/feed/ease

RCOS Dashboard appears to search for an RSS tag, assuming HTML, but as I gave it the actual feed, there is none to find. I'd like to be able to link to tag-specific feeds, but I don't want these cluttering visitors RSS toolbar buttons on my website.

It will be nice to have on the right side of the blog aggregated the links of all the blogs. This may help one to explore a specific blog if he/she is interested in exploring the archives of that blog.

I sort of never tested that...

We're soon going to be using Dashboard for groups other than RCOS. Everything specific to RCOS needs to get pulled out.

It should be possible to point RCOS Dashboard at an actual git url and have it fetch source code information that way.

As the number of projects increases, and the amount of information we wish to communicate increases (as it seems its likely to do) I think we will start running into a problem of too much information to communicate horizontally (I would argue we're already there for smaller resolution screens).

I propose we pull our columns back into a detailed view of the projects that can be accessed by expanding a basic overview. It should give us more freedom and less clutter in the long run.

An example setup:

Have the project name and links to wiki,blog,repo in the basic as a thin row. Click to expand the basic overview and you get detailed wiki/blog/repo information (when, what, who)

Let's make an awesome theme for the RCOS branch of OSS Dashboard. We can probably keep the current theme for the master branch.

It, um, sucks

The Dashboard and Feed views are great, but sometimes you just want to get a pulse of what's new. Something like Facebook's news feed would fit this need well.

Moorthy and Alex Radocea have both expressed their concern about the "update" feature not working. Apparently the new blog posts are not showing up when the update button is pressed. I have not researched further.

We could add a hard-coded check for dashboard in the request URI, and make the home page be the dashboard itself in that case.

Not everybody uses "master"

So Rob can improve the ranking algorithm

We know how many presentations people have given. We should be able to figure out who needs to give one in the near future.

Maybe I'm missing it, but I don't see any instructions for using the dashboard? Not everyone is using the same revision control (github, google code, etc), so maybe a "how to" and an "expected result" for a few different configurations would be useful? It looks like the latest commit message gets posted to the Source Code column? And it looks like the title of the latest blog post gets posted to the Blog column? Is this done automatically even with all the different systems being used?

It says "red = the project hasn't posted that component yet". However, If you click on many of the red ones, even the ones that say "No updates", there is content (awesome-wav blog for example). Am I
misunderstanding something?

In the "Contributors" column it would be great to see email addresses to contact the people involved with the project. Should this be a separate field? Or should we just have the students edit their exiting
"Contributors" field to add the email addresses. Could we automatically implement a "group email" type thing where email could be sent to [email protected] and it would be forwarded to each of the group members personal addresses?

Sometimes things change

Not sure how difficult it would be, or where they would go.

Good for 2 reasons off the top of my head though.

Exposure of the issues list would be a prod for people to adapt another best practice (like the blog, repo, and wiki).
Making it more easily accessible on the dashboard might encourage more cross participation.

There are a few places where I use Group.first or something. These need to get cleaned up so that we can actually support multiple groups. As part of this, the project-group assocation needs to become many-to-many (habtm).

We're starting to add a lot of non-sponsored projects, which don't need to be prodded like the rest. This should be made visually clear.

The current authentication scheme is rather basic; maybe change to a user-centric model? Or at least handle passwords better.

Include Date of last change, short list of most recently changed pages

When adding a blog to the dashboard, it would be nice to simply enter the web url and have the feed url be generated automatically.

I am only familiar with blogspot, but it is simple string concatenation from
http://daviddoriaRCOS.blogspot.com
to
http://daviddoriaRCOS.blogspot.com/feeds/comments/full

maybe it is not this simple with others? There could be a button to "auto determine Feed URL". If it isn't a recognized blog (github, blogspot, etc) then they would have to enter the feed URL manually. It should also send you an email so you can add this system to the auto computable list :)

We need another column for # of presentations given so we can keep track of who still needs to present

For the projects that fall behind by a week or two, we need some system that automatically pokes them to update.

And point it at the new DB server

Example: http://www.google.com/educators/gta.html

128.113.0.0/16
128.213.0.0/16
129.161.0.0/16