-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Poster/Graphic/Infograph that highlights what AsyncAPI does with sponsor's money #672
Comments
@derberg I find this to be pleasant and would be delighted to contribute. |
This issue is part of the AsyncAPI Bounty Program, interested contributors need to follow the guidelines below to ensure fairness and timely completion of assigned tasks: Task AssignmentThe assignment of tasks will be prioritized in the following order:
We encouraged everyone to apply as long as the task is for you (falls under your skill set). We will not be using the first comment - get assigned method for assignments. Instead, we will provide 3 days to consider all individuals interested before assigning any bounty task. DeadlineTo maintain accountability and ensure the timely completion of the deadline for this task will be 6 - 8 weeks from the date of assignment. If a contributor requires an extension on their task, it should be communicated and approved by the maintainer. Issue Tracking and UpdatesContributors must provide weekly updates on the task they are working on to help maintainers stay informed of progress. If a contributor fails to provide an update, they will be reminded via a ping. If a contributor fails to provide an update after three pings over three weeks, we will assume they have silently dropped the issue, and it will be reassigned to someone else. Issue Drop-outsAny contributor who drops an assigned issue will be penalized and will not be eligible to participate in the bounty program for 6 months. We understand that unforeseen circumstances can arise, and dropping an assigned issue may be unavoidable in some cases. However, we believe that enforcing this penalty is necessary to ensure the effectiveness of the bounty program, respect maintainer time, and honor the efforts of other contributors who could have solved the issue but were unable to do so due to the drop-out. We encourage all contributors to follow these guidelines to ensure a fair and timely completion of tasks assigned through our bounty program. |
Thanks @thulieblack |
@derberg it 3days now 😉 |
oh yes, I'm blocked a bit with #673 @Mayaleeeee but yeah, go ahead and start working on the issue, you know what is the scope, in linked PR you see content, so you can already start drafting the idea |
Alright @derberg |
Hello @derberg, would it be possible for you to provide access to the raw data in PDF format? |
Hi @derberg and @thulieblack, @durberg I propose presenting the information in an infographic format, enabling users to easily view the data at a glance rather than relying on textual explanations. Furthermore, I developed some wireframe ideas for the project last week, which can be viewed below. I would appreciate it if you could review them at your earliest convenience and provide your feedback. |
hey, thanks @Mayaleeeee !!! I like the form and shape it is getting in regards to infographic style, shouldn't the first part (where open collective and other forms are mentioned) be also done in more graphical way, so LF/OC/GH are also represented with logos for example? in case of expense breakdown, where will be descriptions visible? like description of who we hired, or the description of bounty? in case of chart, it will be hard to present the income, it is pretty complex topic at the moment:
|
@Mayaleeeee fyi, the file that is supposed to be a source for the infographic is updated -> https://github.com/asyncapi/community/blob/master/PROJECT_FINANCE.md |
Thanks @derberg I'll take a look at it soon |
Hey @Mayaleeeee how's the projecting going any updates |
Hi @thulieblack I'll be providing the update as soon as I get home, I'm currently on transit. Thank you. |
Hey @derberg, sorry for the delay. I just wanted to update you and share the correction I made to the design. |
nice 😍 the logos, they have different size cause you use logos with project names. They kinda look "crowded". How about using dark version for all logos? and larger spacing? I don't have a clear suggestion, sorry what I'm missing in design is:
all these sections are in https://github.com/asyncapi/community/blob/master/PROJECT_FINANCE.md |
Thanks, @derberg I apologize for not including the other sections earlier. I will make sure to add them now. Regarding the icon colours, I plan to use the logos as a reference and change the icons to dark colours in the wireframes. Once the design is approved, I will restore the original colours of the logos and incorporate the AsyncAPI colours into the website. Does that explanation make sense to you? I still need to complete the other sections, but I can share that specific section for you to review. |
Hello @derberg , I wanted to provide you with an update on the design I've been working on. Could you review it and let me know if there are any additions or deletions you'd like me to make before proceeding to the Hi-fi stage? Your feedback is highly appreciated. |
Oh it is perfect ❤️ I guess what left is icons? like for example in section about other financial support? as now it looks like 4 identical boxes with same icons |
ok cool, so I should wait? right? |
Oh, the only remaining thing is to get that done, right? If that's the case, I'll have it completed before the end of the day. Regarding the chart section, I just wanted to clarify if I should manually input the expenses from here or if you have any other suggestions in mind. |
what do you mean by "manually input"? |
Hi @derberg the icons have been updated here. Please check it out. |
it looks awesome ❤️
there is no way to do it in automated way for now, and also manual will be hell, so for now we need to hide this section, that will come later |
Thanks Lukasz. Is there anyother thing I need to do here? |
so initially the goal was to get this as PDF. I had no idea you will actually instead make a beautiful design of the website ❤️ before someone adds it to the website, it will take some time. I was wondering if I can get a PDF version as a temporary solution? without website header and footer, without budget analysis but with clickable donation links? |
Thank you so much. So, we would like the Linux, Open Collective, and GitHub icons to be clickable, directing users to their respective pages, right? I think the PDF might be a viable option, although I'm uncertain about its compatibility with the clickable icons. Nevertheless, I'll give it a try. |
Please confirm the links are clickable from the pdf files here. |
ah, they are not so can you replace buttons with visible links? |
Yes, that's what I did, and it's clickable here on both mobile and desktop. However, it appears somehow strange on mobile. Check the mobile video |
ah sorry, they are clickable, I just was clicking wrong buttons, |
ah, and last thing, since there is no website header, can you add some generic asyncapi header or logo at top? |
Yeah, this will work |
Take a look at them. |
super nice, thanks a 💯 can you create a follow-up issue in website? for implementation? with all details, icons, figma-if that is what you used and whatever is needed for contributors to add this new view? congrats on completing I think first in history bounty issue, and looks like first in history design issue that we will pay for! @thulieblack on to you I guess |
You gotta be kidding me, it's done already? 🤩🤩, Congratulations @Mayaleeeee. |
The next step is to submit an expense on open-collective |
Thank you so much 🤭✨✨🥳 |
Thanks a lot Thulie ❤️❤️ |
@Mayaleeeee one tiny change to PDF is needed, become a sponsor should link to https://opencollective.com/asyncapi not github sponsors 🙏🏼 |
I wanted to ask you this yesterday 😅. |
Alright Thulie. |
Updated |
Should I create it as a bug or feature request? @derberg |
feature-request |
Thank you |
Done, you can see it here. |
thanks so much. I just transferred the issue you created under website repo @Mayaleeeee your open collective expense is approved. from my perspective the issue is implemented, closing Thanks a 💯 |
Reason/Context
On regular basis I'm having conversations with different potential sponsors and it would be nice to have a nice summary of what we do in a nice graphical way, and not raw data in PDF.
I think the strong side of our community is the transparency of how we spend money and that we invest them back into the community.
We just need to make this data available in one place in an easy-to-digest way.
Description
AsyncAPI income and spending
- if you have a better name, please suggestThe text was updated successfully, but these errors were encountered: