Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collect functional requirements #1

Open
hkakutalua opened this issue Sep 3, 2018 · 8 comments
Open

Collect functional requirements #1

hkakutalua opened this issue Sep 3, 2018 · 8 comments
Assignees

Comments

@hkakutalua
Copy link
Contributor

hkakutalua commented Sep 3, 2018

Collect functional requirements for the application by talking with the customer.
Functional requirements can be brainstormed inside the team or tweaked if needed.
Top level priority "should" be given to immediate functionalities for the first version of the app.

@hkakutalua
Copy link
Contributor Author

@pedromassango, could you please talk with any Rapidinho employee to collect relevant functionalities (and of course take note of all them)? Before the weekend would be perfect.

You can also pass his/her phone contact to us, so we can (re)collect as well to be sure, right now it's impossible to create a reunion with the presence of all of us.

@pedromassango
Copy link
Member

I will talk with someone in saturday.

@pedromassango
Copy link
Member

I gues that we should not use their name as the name of the project, but the name of the app like Delivery App

@hkakutalua
Copy link
Contributor Author

hkakutalua commented Sep 3, 2018

Yes, i agree with your last point, for one reason particulary: this is a open-source project with a very permissive license, i do agree that we should keep the license as is, so that people know that GDG Luanda organizers made the app.

But, i recommend we change the name of the app to a generic one, in the future people will fork/copy the project code, so it's not cool to leave Rapidinho name in the code.

My plan it's just to create the app for our sake and free-time, and then show them to evaluate and maybe sell. If we reach that phase of selling them the app, we will of course create a private fork from this project. That's just my vision, what do you think?

Of course, creating a fork and maintaining it up to date with the original code will be a pain, so in that case the second option would be maintain all our work open-source with the app name as rapidinho to simplify things.

@braulio94
Copy link
Member

Let's talk to Rapidinho team (though we kinda have already) and see what they say.
If they're ok with us using their logo and name we keep developing otherwise we change it to a generic name as @Henry-Keys suggested.

@hkakutalua
Copy link
Contributor Author

@braulio94, we can do that otherwise.

@pedromassango
Copy link
Member

pedromassango commented Sep 8, 2018

I talked with one of Rapidinho's employee, unfortunately she doesn't have any information about the app requeriments. She will talk with her boss to talk to speak with us next saturday.

@braulio94
Copy link
Member

Thanks @pedromassango.

The idea was not to ask them for the app requirements, it's simply to let them know that we're building this app and we're using their brand name and logo.

Basically, we just want their consent.

@pedromassango pedromassango removed their assignment Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants