u/Fearless-Daikon5763

Hi! I have a research tool that I am developing for my own research and expect it will be used by others (by tens or hundreds of users), but the program is under perpetual development. I am adding new modules and capabilities at about the same rate that I am debugging and polishing. I am afraid if I release an imperfect version and make it open source, someone can just improve it a release a more stable and user friendly version within a week. A large research lab can also direct resources toward superseding my efforts in a week. I obviously want credit for my original ideas and contributions, so wondering what a normal path may look like. I could first share the software with colleagues, but then it will be released partially and likely stall in the slow-as-molasses pace of academia. Is there a coding guru that can anonymously review my software, is there a consensus in the “rules of engagement” for first releases of a useful but imperfect software bundle?

"As Graduate Chair, I am not in a position to evaluate scientific disagreements, project ownership, authorship, or other research-specific matters. These issues are best addressed through discussions between you, your supervisor, and your supervisory committee."

The grad committee has not responded to two emails, which is why I emailed the grad director. Supervisor is not responding to emails or having meetings for ten weeks.

On a scale of 1 to 10, with 1 being totally unengaged and 10 being incredibly helpful.

Took my child to Greenwood Manor Park and there was an old white guy tossing the ball everywhere for his pooch, including onto the playground. I requested him to leash his dog but he claimed the dog wouldn't bother us. (Isn't that what all dog owners say?) At one point the ball almost hit my head, followed by a not very regretful 'sorry'.

Needless to say we won't be back again. Thought it would be a change from the usual parks but I don't want a 70lb dog thundering around while we're trying to get some relaxing outside time.