search

LBNL-AMO-MCTDHF / V1

LBNL-AMO-MCTDHF v1.36! . . . . .
https://commons.lbl.gov/display/csd/LBNL-AMO-MCTDHF
Other
12 stars 3 forks source link

New code requirements, user-requested features -- where does this go on the github website #4

Closed LBNL-AMO-MCTDHF closed 9 years ago

LBNL-AMO-MCTDHF commented 9 years ago

Folks -- I'm wondering: Let's say a user wants us to implement a feature in the code. A new action perhaps, something trivial. Or, let's say one of us notices a bug, but is too busy to fix it. Where do pending issues with the code go, on the github website? Things that have not yet been attended to, but should be attended to in the future. We need a LBNL-AMO-MCTDHF to-do list. Dan

LBNL-AMO-MCTDHF commented 9 years ago

...perhaps more precisely a LBNL-AMO-MCTDHF/V1.0BETA.030315.INTELFFT to-do list.

djhaxton commented 9 years ago

...hey I was wondering that too! naD

djhaxton commented 9 years ago

... perhaps the place where these things go is right here, issues. However I want something different. I am thinking that issues are things that are current problems (issues, "he/she has issues") with the code. I want something for the future. A past/future division, or current/future division, or whatever. I want a section for plans for the future, separate from issues.

danhax commented 9 years ago

gosh that's really interesting.

danhax commented 9 years ago

I hesitate... are users allowed to comment on issues?

djhaxton commented 9 years ago

Yeah man! Go ahead.

djhaxton commented 9 years ago

I think we need a wiki. Issue closed.