Transform your stories into captivating comic art with dialogue effortlessly! this project harnesses the power of GeminiAI and stable diffusion for processing and generating stunning images and dialogues
Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.
We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
Some suggested prompts/questions you can add to a “Report Bug” template are:
Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:
Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?
Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to yours.
As the repo maintainers have to manually close an issue after merging a PR linked with that issue, I propose a workflow where the issue linked with a PR which be automatically closed when that PR is merged by the maintainer and efforts will be saved.
GSSoC2024
Instead of getting it on the email. The user can download it from the page where she/he provides the dialogue.
I want to take up this issue
I am little bit unsure if this could be done, but I guess there is always a yml file we could make which adds tags from issue to PR
N/AN/A
Other
I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.
I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.
Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.
No response
👋 Hi @Girishbari ,
I am Prince,web developer Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program
Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.
As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.
This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.
If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.
I look forward to working with you 
Creation of Template for Issues:
No
https://www.figma.com/design/Vc88ZJOcx6QtxS7ARU2l6g/Untitled?t=0RvYpLsxkn4GGxxj-1
Currently, frontend lacks a landing page, I am adding some screenshot and Figma design
I am also open to what you suggest, maybe drop any good Figma file you have
Try to use radix-ui and its theming system, don't add extra dependencies until it is essential, this is frontend heavy task so this issue may require 2 contributors at the same time or regular communication with me
GSSoC2024
while there is #40 pending, we could add a login page in the frontend note that make use of existing components in component directory
N/AN/A
GSSoC2024
I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository. The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."
Please assign this issue to me
I will write an Github Action's workflow that will automatically generate comments by github bot in the issue whenever an new issue is being created.
GSSoC2024
Over time, repositories can accumulate a large number of open issues, including some that may no longer be relevant or actively worked on. Manually closing these old issues can be time-consuming and tedious.
I would like a workflow that automatically identifies and closes old issues based on certain criteria, such as no recent activity or being open for a specific duration.
GSSoC2024
Currently there is express server added and Sign in route is made, remove signing route and refer to this doc
https://trpc.io/docs/quickstart
You'll have
1. remove the signin route
2. study how TRPC is implement in monorepo and nodejs
3. add the connectionN/A
Other
Refer to this repo https://github.com/Sanchitbajaj02/palettegram, see how appwrite instance is integrated do the same in nodejs
NanNo response
Other
I am requesting the implementation of a feature that automatically comments on an issue when it is closed in the project repository. This comment will serve as a closing remark, thanking the contributor for their input and providing any necessary follow-up information or next steps.
Implementing this feature would enhance the project's workflow by:
Providing immediate acknowledgment to contributors when their reported issues are resolved.
Standardizing communication and ensuring that contributors are informed about the resolution status of their reported issues.
Improving transparency and reducing ambiguity in the issue resolution process.
This feature would streamline collaboration and contribute to a more efficient and user-friendly experience for all project contributors.Additional context
GSSoC2024
new
Over time, open pull requests (PRs) can accumulate in a repository, cluttering the interface and making it difficult to focus on active development tasks. Additionally, outdated or abandoned PRs may no longer serve their intended purpose and should be closed to maintain repository cleanliness.
Implement a workflow that automatically closes old PRs based on predefined criteria, such as their last update timestamp. By regularly closing PRs that have not been updated within a certain timeframe, the repository can stay organized, and contributors can focus on active and relevant PRs.
GSSoC2024
I would Like to Work On This.
Update node app with sign-up route, also make sure all the necessary checks are made then only do res.json({ message: 'success'})
REMEMBER
not to add any db connection as one issue is already made on it, just make a route and apply checks**
a
a
This documentation request is to update the README.md file by adding a table of contents. Currently, the README lacks clear navigation for users to find relevant sections quickly. Adding a table of contents will improve readability and user experience.
Why Ts and why not pure vanilla js?
TypeScript stands out from vanilla JavaScript with its outstanding features like static typing, interfaces, enums, generics, union types, type guards, and decorators. These features collectively enhance code quality, readability, and maintainability, while also significantly reducing the occurrence of bugs and errors. By providing a more structured and expressive way to write code, TypeScript empowers developers to build complex applications with confidence, offering a smoother development experience and facilitating collaboration within teams.
Why I am the right fit for this project
I've successfully utilized TypeScript across projects integrating React-Three/Fiber, React-Three/drei, Three.js and React Spring into Next.js for immersive 3D websites, implemented WebRTC and sockets in TypeScript codebases, and built scalable solutions with Gatsby, GraphQL, and TypeScript, all with a focus on robustness and efficiency. I think I have required know-how on how to handle the TypeScript codebases.
Here is how I will handle my js to ts conversion
Install TypeScript: I will begin by installing TypeScript globally using npm or yarn.
npm install -g typescript
Rename Files: Change the file extensions of all JavaScript files to TypeScript files. For JSX files, I will change the extension to .tsx.
Enable TypeScript Configuration: If project doesn't have a tsconfig.json file, I will create one using the following command:
tsc --init
Start Converting: Begin converting my JavaScript code to TypeScript by following these steps:
let firstName: string = 'John';
let age: number = 30;
function add(a: number, b: number): number {
return a + b;
}
interface Person {
firstName: string;
lastName: string;
age: number;
}
let person: Person = {
firstName: 'John',
lastName: 'Doe',
age: 30,
};
Clean Class Design: When converting existing JavaScript classes to TypeScript, refactor them to adhere to clean and object-oriented design principles, ensuring the new TypeScript codebase is more organized and maintainable.
Enums: Replace constants with enums to improve code readability and maintainability.
enum Color {
Red,
Green,
Blue,
}
let c: Color = Color.Green;
console.log(c); // Output: 1
function identity<T>(arg: T): T {
return arg;
}
let output = identity<string>('hello');
console.log(output); // Output: hello
let value: string | number;
value = 'hello';
console.log(value); // Output: hello
value = 42;
console.log(value); // Output: 42
function printName(name: string | string[]): void {
if (typeof name === 'string') {
console.log(name.toUpperCase());
} else {
console.log(name.join(', '));
}
}
printName('John'); // Output: JOHN
printName(['John', 'Doe']); // Output: John, Doe
let x = 3; // TypeScript infers that x is of type number
console.log(x); // Output: 3
interface Person {
firstName: string;
lastName?: string;
}
let person: Person = {
firstName: 'John',
};
console.log(person.lastName?.toUpperCase()); // Output: undefined
@sealed
class BugReport {
type = "report";
title: string;
constructor(t: string) {
this.title = t;
}
}
function sealed(constructor: Function) {
Object.seal(constructor);
Object.seal(constructor.prototype);
}
When @Sealed is executed, it will seal both the constructor and its prototype, and will therefore prevent any further functionality from being added to or removed from this class during runtime by accessing BugReport.prototype or by defining properties on BugReport itself.
Additional things I will consider While converting the Js codebase to Ts codebase :
Resolve Compilation Errors:
As I convert your code, TypeScript might raise compilation errors due to type inconsistencies or other issues. I will make sure to address these errors one by one by refining your type annotations and ensuring compatibility with TypeScript's type system.
Incremental Adoption:
If the codebase is extensive, I will consider adopting TypeScript incrementally. I will start by converting individual modules or components and gradually expand the TypeScript coverage across the project.
Testing and Validation:
Test the TypeScript code thoroughly to ensure it behaves as expected. Use TypeScript's type system to catch errors early in the development process, reducing the likelihood of runtime issues.
Continuous Integration:
Integrate TypeScript conversion into continuous integration pipeline to ensure that new changes adhere to TypeScript standards and do not introduce regressions.
Documentation and Training:
Update project documentation to familiarize team members with TypeScript features.
there is a packages folder in Monorepo that can be utilized for all UI components, you will have to move the components and update all the respective import statements
nannan
GSSoC2024
Yes, the feature request is related to a problem. When pull requests (PRs) are merged in a project, it is often important to provide consistent feedback or notifications to the contributors. Currently, this process can be manual and time-consuming, leading to inconsistent communication and delayed acknowledgments. This can frustrate both maintainers, who have to remember to comment, and contributors, who might feel their efforts are not promptly recognized.
To enhance our communication and acknowledgment process, we're implementing an auto-commenting feature for specific events within our project repository. This feature will automatically generate comments under the following circumstances:
PR Merged: Upon the successful merging of a pull request (PR), an auto-comment will be added to the corresponding issue, indicating that the PR has been merged and expressing gratitude to the contributor for their valuable contribution.
Additional context
GSSoC2024
Currently project has nextjs and node app in one singular which seems to be workable not good for long run I suggest converting current repo into mono repo or into workspaces one could use turborepo, pnpm workspaces
https://turbo.build/repo/docs/getting-started/add-to-project
Changes will require some code refactoring in node app, so I will be available here once conversion is done I would guide further
I noticed Readme does not have a direct link to set up a project, you can add a link with helpful message in How to contribute
No response
Enhancement I would like to enhance the landing page design using Figma
Additional context
GSSoC2024
We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.
Please follow these instructions on how to add a Code of Conduct.
Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md
Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.
Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md
I want to add MIT License to this repository, please assign the issue under GSSOC'24
No response
In GSSoC'24, GitHub Topics will help the discoverability of your project.
I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.
If you are happy with the topics you have, feel free to close this issue. 👍
I have added labeler.yml, but it does not seem to work properly
Update it if required and make one random issue named labeler checker I will remove it later, once I verify labeler.yaml is working
NanNan
Other
As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.
Recommendations:
Add issues of varying difficulty to the repo often. you must add the tag GSSoC'24, Level 1, Level2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues
while there is #40 pending, we could add a rergister page in the frontend note that make use of existing component that is present in component section
N/AAdditional context
Other
which .env/.env.locals files to be updated before running code
proper description for that needs to provided into environmental variables for project execution requirements
No response
Currently we've pnpm installation in setup.md, convert the all the base commands into following
cd comic-cult
install dependencies
npm install
run whole project
turbo dev
make sure to have turbo as global dependencies
npm install turbo --global
run server only
cd apps/server && npm run dev
run client only
cd apps/client && npm run dev
No response
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.