We have a formal project homepage now! Thanks for the reminder. https://whimsical.apache.org/
I think the best ways to get started are to post ideas here on the mailing list, or actual bugs (or *major* changes) as JIRA issues. And then just use github branches/PRs for development. Sam Ruby wrote on 4/20/17 4:11 PM: > On Thu, Apr 20, 2017 at 2:48 PM, Michael Wall <[email protected]> wrote: >> Great, thanks for the response Sam. Appreciate the link to agenda.rb too. >> >> I'll checkout the code and see what I can get running locally. Is there >> anything in particular the project needs? People interested either in 1) fixing up little bits of various scripts, or 2) deploying new tools in a simple environment that can directly access bits of Apache organizational data (much of which is committer- or member-private). Personally, I've been using this as a way to teach myself ruby, and have been starting by improving styles/organization of some of the individual tool output pages. In particular, I'd like to build a template script for the "visualize this internal data" case, including improving the whimsy/asf/themes.rb support so that tools can have consistent output with minimal effort by individual tool writers. The Whimsy production server environment provides both a traditional ruby on rails / httpd server, plus a variety of helper classes that access SVN, LDAP, and other specific bits of data inside Apache corporate operations. It's great for prototyping new organizational process helpers and some kinds of data visualization for rosters, historical board minutes, etc. Important notes about the code: - The Whimsy PMC supports the server. Individual developers support their own tools. - Most tools are independent, but use the core lib/whimsy/asf module to access organizational data. - Code checkins are *auto-deployed* to the live server every 30 minutes. Personally, I would love a new developer to review DEVELOPMENT.md and MACOSX.md and provide any patches to fix bugs or make the instructions clearer - something that makes it easier for newcomers to get started. Welcome! > > You didn't specify your development environment. :-) > > If you are coming from Windows, things aren't likely to work. Since I > see references to shell scripts in your github repositories, that > isn't likely to be a problem. > > If you want to get the agenda tool up and running, there is a > Dockerfile and a Vagrantfile, so you can run this tool in a container > or a VM respectively. That will also give you a good idea of what you > would need to do if you run Linux. > > As to what needs to be fixed: I'm probably not the person to ask. If > others don't speak up: pick a tool that doesn't work the way you would > like, and I (and others) can talk you through what it would take to > fix it. > > If you want something more meaty... I'd love to see the board agenda > tool either have a React Native version for iPad and/or Android; or > to exploit service workers so that it can load as instantly as it > currently changes pages. Offline support would also be handy... allow > Directors and others to approve reports, make comments, and even flag > reports when offline and upload their changes when they next have > access to the network. This would also help the secretary when he has > network problems during the meeting. > >> Mike > > - Sam Ruby > >> On Thu, Apr 20, 2017 at 12:16 PM Sam Ruby <[email protected]> wrote: >> >>> On Thu, Apr 20, 2017 at 9:43 AM, Michael Wall <[email protected]> wrote: >>>> Hello, >>>> >>>> After filing my first board report for Accumulo through Whimsy, I was >>>> interested in seeing what the site was doing and understanding it better. >>>> Things like how it manages to commit to svn without conflicts. I didn't >>>> even realize it was an Apache project. Took me a minute to figure out >>> the >>>> mailing list was whimsical.apache.org < >>> [email protected]> vs >>>> whimsy.apache.org too. >>>> >>>> From the main site at http://whimsy.apache.org, it is not apparent how >>> to >>>> contribute. On the github project at https://github.com/apache/whimsy >>>> there is one issue and two pull requests. Is this project in need of >>>> active development? >>>> >>>> I see from the roster at >>> https://whimsy.apache.org/roster/committee/whimsy >>>> that all members of the project are foundation members. From the >>> previous >>>> reports there was mention of growing the development community. Is this >>>> project only for foundation members and is there still a need/desire to >>>> grow? >>> >>> There definitely is a desire to grow! >>> >>> It looks like our website is an intelligence test. The good news is: >>> you passed! :-) >>> >>> I don't know how much of an impediment being a non-ASF member will be; >>> certainly some tools require access to foundation private data. I >>> know that at least at one time, the board agenda tool could be run >>> independently, and even has test data. >>> >>> A quick browse through your github account, and you clearly have >>> skills that could help. Whimsy tools tend to use react not angular. >>> >>> My preferred development environment is Ubuntu, but most others use >>> Mac OS/X. If you are like most others, here is a place to get >>> started: >>> >>> https://github.com/apache/whimsy/blob/master/MACOSX.md >>> >>> If you have any questions, here is the right place to ask them! >>> >>>> Thanks, >>>> >>>> Mike Wall (mjwall) >>> >>> P.S. To satisfy your curiosity on svn commit: what the board agenda >>> tool does is check out a fresh copy, apply the changes, and commit >>> real fast; and if that doesn't work the first time, try up to 20 >>> times: >>> >>> >>> https://github.com/apache/whimsy/blob/master/www/board/agenda/models/agenda.rb#L113 >>> -- - Shane https://www.apache.org/foundation/marks/resources
