blender/flamenco
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Website: update GSoC text

Browse Source 
I've taken out the plagiarism thing, and added a "become familiar with
Flamenco" thing.
This commit is contained in:
Sybren A. Stüvel 2025-04-05 10:12:59 +02:00
parent f298e5d03b
commit 31096b34a7
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
web/project-website/content/development/gsoc/_index.md
View File

@ -21,6 +21,11 @@ the copyright status of AI-generated code is dubious, and you may not have
permission to share the code and claim that you wrote it. As such, AI-generated permission to share the code and claim that you wrote it. As such, AI-generated
code cannot be accepted. code cannot be accepted.
**Become familiar with Flamenco**. Your proposal should also contain some form
of planning. You can't plan your work if you have no experience with Flamenco,
and haven't made any code changes to Flamenco yet. Without that experience, it's
not a plan but a wish list.
Another way to increase your chances: **don't over-sell your skills**. Using Another way to increase your chances: **don't over-sell your skills**. Using
Flamenco once or twice is not enough to say you "*know Flamenco*". If you don't Flamenco once or twice is not enough to say you "*know Flamenco*". If you don't
know all of the programming languages and techniques used in the project, that know all of the programming languages and techniques used in the project, that
@ -29,14 +34,6 @@ used Go*" is fine, but do make it explicit that this is the case, and also
explain why you think it's fine to still apply for joining this Go-based explain why you think it's fine to still apply for joining this Go-based
project. project.
When you link to your work to show off your skills, that's great! But make sure
that it is clear **what was written by you, and what was written by somebody else**.
If the Git history only has commits in your name, and there is no description
like "copied code from ${LOCATION} as a starting point", then realise that the
rest of the world will think this is your code. Be careful, this could be seen
as plagiarism. Many Open Source licenses require you to credit the original
authors.
And finally: **be part of the community**. Join the chat, use Flamenco, get And finally: **be part of the community**. Join the chat, use Flamenco, get
involved. Communicate with your mentor. If you have questions, pop in the involved. Communicate with your mentor. If you have questions, pop in the
Flamenco chat channel and ask them (but please also scroll back a little to see Flamenco chat channel and ask them (but please also scroll back a little to see