Project Intake v2

[mscarey]

Not many people are starting projects through open-austin.org's project page or project process page. We should think about redesigning the interface for project onboarding, which currently flows from our project page to our github project-ideas issue tracker.

I'd be curious whether people are getting to the projects page but just not finding the interface convenient enough to start on a project, or whether they're not going to the projects page at all.

[thebestmensch]

Looks like we have google analytics set up on our site (https://github.com/open-austin/open-austin.github.io/blob/bc2e114cc03dfc49410b4df992af4515171b8331/_includes/google-analytics.html#L7), can someone give me access to the dashboard please? @mateoclarke @VictoriaODell

@mscarey what do you think adding project "types"? E.g. Idea, Idea w/ external stakeholder, Ongoing, etc. Idea here is to give folks a sense of project stability.

[mscarey]

We have a few YAML fields now that try to categorize projects: Type (e.g. website), Status (archival, in development, or deployed), cfa stage (Experiment, Alpha, Beta, etc.), and Archived (a boolean). I think type and status aren't actually shown to users on the website. Archived is used to determine which page projects appear on, but we could probably eliminate that field and accomplish the same thing with Status.

[thebestmensch]

Formally kicking off this project! Here's the brief and the project issue.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mateoclarke]

Don't think this should've been closed. There were folks working on it at the last Community Action Night on 4/1.

[thebestmensch]

That is correct, apologies for missing this. I'm going disable stale bot in the iced-coffee repo, but I still think we need some sort of issue management for the project-ideas repo (#336). Best time to revisit that is probably after we redefine what project intake looks like in this project.

[thebestmensch]

This has taken a bit of a backseat for more immediate priorities (#355 and #354 chief among them) and I feel like I'm bottlenecking progress. Any interest in taking ownership here, operationally or entirely, @mscarey or @olitreadwell?

[mscarey]

@olitreadwell and I discussed adding a github widget to the projects page that would provide some kind of view of project activity or open issues, to make it easier for people to get involved from there. A cursory search didn't turn up any good widget for doing what we wanted. My very limited Ruby makes it hard for me to make structural changes to the Jekyll site.

I think I'll try pruning the project-ideas issues, which I see @VictoriaODell did a while back. I think it's a little awkward for us to take all the descriptive tags off the older ones and replace them with an "inactive" tag, but still not close the issue. It would probably be better if people could still search for older ideas based on the tags. If by "inactive" we mean we never want people to find the issue or work on it ever again, it would be better to close the issue than delete all the tags. And the "inactive" tag (similar to the "stale" tag we've been discussing lately) doesn't help users much because they could see the lack of activity anyway by checking the date of the last comment.

[mateoclarke]

I like the approach of closing out inactives instead of tagging. Also noting that Javascript is an option for pulling in data into Jekyll from 3rd party sources. Probably would need to be that anyways to pull data asynchronously from Github each time a user visits the page. If it were in Ruby, updates to the project listing would only update on site rebuild. Jekyll isn't dynamic, its static. But you could write Javascript that is dynamic on top of the static pages. Make sense?

[lianilychee]

closing - stale