Git Product home page Git Product logo

general-discussion's Introduction

General-Discussion

A place for discussing all apps in general + anything else you want to say.

FAQ

How do I suggest an improvement, ask a question or report an issue?

  1. This general discussion repository is used for bugs and suggestions that affect multiple apps. For issues affecting only 1 app, use its separate repository.
  2. If you are reporting a bug, provide steps for reproducing, and mention your app and OS version.
  3. Ensure you use the latest app version and read the in-app FAQ before reporting anything.
  4. Check if the issue has already been reported. Use search with some keywords.
  5. If the issue is already reported, give it an upvote to increase its priority.

Contribution rules for developers

  1. Every project contains a .editorconfig file, with definitions of required indentations, newlines, etc.
  2. Always format the code (Ctrl + Alt + L) and optimize imports (Ctrl + Alt + O) before creating a pull request.
  3. If you add a new icon, make sure it is prefixed with "ic_", it is white, and try using vectors.
  4. If you change something in the UI, test the visibility with all themes, including Black & White and System default (Material You) on Android 12+. Test the changes by using the biggest system font size too.
  5. Use the existing code style and naming conventions; do not bring your own style.
  6. Always use brackets, even at 1 liner "if", "return" or "continue" statements, etc.
  7. If you add a new model or work with Gson, test the build in release mode with Proguard enabled as well.
  8. There is no real functionality change between build flavors, only some About button visibility differences, Rate Us dialog, and More Apps From Us buttons not showing up or so.

If you try fixing a bug or adding a new feature, make sure that it is already reported at the given repository and the report is open without label needs triage. If the given issue is closed or still has needs triage label, your pull request will likely be rejected. The only exceptions are critical bugs that we weren't able to classify yet.


How can I suggest an edit to a file?

Creating pull requests with some changes is a lot simpler than most people think. Most suggestions are related to translating strings, there are 2 ways to do it.

You can find our apps on Weblate at https://hosted.weblate.org/projects/fossify/, you can see untranslated strings there easily.

However, if you prefer the old-style file updating via Github, you can still do it. The process is the following:

  1. Log in to GitHub.
  2. Find the file with the strings (app/src/main/res/values(-xx)/strings, for example, the Italian translation of the Gallery is at https://github.com/FossifyOrg/Gallery/blob/master/app/src/main/res/values-it/strings.xml).
  3. Click the pencil button at the top right corner of the file.
  4. Edit the file with your suggestions.
  5. Add a commit message under the file, to the text field which has a hint similar to "Update strings.xml". Just type in what you have done, for example, "updating Spanish strings".
  6. Click Propose file change.
  7. Click the green button Create pull request.
  8. Thank yourself!
  • Change only the string which is between ">" and </string>, not the first one after the "name=" tag, also not the strings between <!-- and -->.
  • Please escape apostrophes, meaning you have to put a backslash before every apostrophe to make it look like: \'

To find the proper language file at the Gallery, go to https://github.com/FossifyOrg/Gallery/blob/master/app/src/main/res, then look for a "values-[language code]" folder. Use the strings.xml file inside it. If you can't find your language code, the file might not be translated to your language at all yet, and you will have to create a whole new file.


How do I add a new file?

You will most likely want to add a new file only if you translate an app into a new language. Doing it is actually not difficult at all, just read on.

  1. Log in to GitHub.
  2. Find the place where the new file belongs. If it's really a translation of the strings in a new language, go to app/src/main/res, for example https://github.com/FossifyOrg/Camera/tree/master/app/src/main/res.
  3. At the top right corner click at Create new file.
  4. After the res folder, you can type in your folder path. For creating a German translation just type in values-de/ (where de is the country code). The new folder will be added automatically after typing the slash.
  5. Add a file name, i.e., strings.xml (the path should look similar to the image below) Github new file path
  6. Copy the contents of an already existing strings.xml file into the new file (for example, the content of https://github.com/FossifyOrg/Camera/blob/master/app/src/main/res/values/strings.xml).
  7. Add your string translations.
  8. Add a commit message under the file, to the text field which has a "Create new file" hint. Just type in what you have done, for example, "adding Spanish strings".
  9. Press Propose new file.
  10. Click the green button Create pull request.
  11. Thank yourself!
  • Change only the string which is between ">" and </string>, not the first one after the "name=" tag.
  • Please escape apostrophes, meaning you have to put a backslash before every apostrophe to make it look like: \'

general-discussion's People

Contributors

tibbi avatar naveensingh avatar aga-c avatar

Stargazers

Burden Haze  avatar  avatar Ahmed ElSamha' avatar  avatar Leon Friedrich avatar Internet Yamero avatar  avatar Lendary Sayajin avatar dCo3lh0 avatar Atik Shakil Attar avatar Max Mignolet avatar Sicco van Sas avatar Nicholas Orchard avatar Aryan Chauhan avatar  avatar  avatar Nikolaus Schlemm avatar Luka Đ. avatar အဆွေတော် avatar Andrew Chou avatar Alex Hall avatar SagXD avatar  avatar  avatar  avatar Colby avatar 名前ない avatar Hana Burtin avatar Chris McCormick avatar Balázs János Varga avatar Artem Smaznov avatar Wojtek avatar  avatar dgw avatar  avatar DanielN avatar Benoit de Chezelles avatar  avatar Flamez avatar Sunny avatar  avatar  avatar  avatar ronnie@machine avatar  avatar Matt Snider avatar  avatar Luca Andrea Rossi avatar  avatar  avatar Ⱚ avatar freshgum avatar Simon Thyregod avatar Michael Köppl avatar galacticDust avatar  avatar  avatar inson1 avatar  avatar  avatar  avatar

Watchers

Neustradamus avatar  avatar  avatar  avatar Haylee avatar  avatar  avatar inson1 avatar  avatar  avatar  avatar John avatar

general-discussion's Issues

Redesign icons and other artwork

Hi,

Up-front: I am not a lawyer. But my understanding of forks of FLOSS software is that usually, the branding and artwork is not covered by the GPL.

I don't want to add to the high-priority things here, but considering the party that upstream is getting sold to, it would probably be wise to figure out the copyright- and trademark-status of the artwork and branding present in the repositories and get replacements in place.

localized datetime formats

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs), in the README and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report may get dismissed otherwise.
  • This issue contains only one feature request.
  • I optionally donated to support the Fossify mission.

Which apps should have this feature?

No response

Feature description

japanese locale example:
image

Why do you want this feature?

proper localization

Additional information

https://en.wikipedia.org/wiki/Date_and_time_notation_in_Japan
https://developer.android.com/reference/kotlin/android/text/format/DateFormat#getbestdatetimepattern
https://developer.android.com/reference/kotlin/android/icu/text/DateFormat

Testers for Google Play

Discussed in https://github.com/orgs/FossifyOrg/discussions/57

Originally posted by naveensingh December 24, 2023
This is sad news for those who waiting for Google Play releases.

For new developer accounts (such as Fossify), it is now a requirement to have at least 20 testers opt-in on a closed track before the apps can be published on the production track. We have to run closed tests for at least 14 days before applying for production.

If you are interested in helping out with this, please share your email IDs. You'll be added as a tester on the Fossify Google Play Developer account. When you get an email, please install the app(s). If you want to avoid sharing your email ID publicly, send it to [email protected]

About github-forks

The projects are "github-forks" of the original projects:

fork

This might not be a good idea:

Deleting your repository or changing its visibility affects that repository's forks.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility

In practice, the impact should be limited if the original repo is deleted though:

Deleting a public repository

When you delete a public repository, one of the existing public forks is chosen to be the new upstream repository. All other repositories are forked off of this new upstream and subsequent pull requests go to this new upstream repository.

Suggest creating a nonprofit or Foundation to protect the name, new icon logos and URLs

My suggestion is that in the future the name "FossifyOrg" brand, the logos of each icon created and even the URLs of the F-Droid version and perhaps the Playstore could not be sold again by someone here, as the main person responsible for this new Project.

Note that I'm not referring to the source code, which can be created as a fork, I'm referring to what can be copyrighted.

That's why I suggest that lawyers and people with knowledge of law study possibilities such as:

  • 501c3 nonprofit in USA (like signal.org)
  • Foundation in Switzerland (like Quad9 DNS Foundation)
    -Private Limite Company with Apache License 2.0 (like Organic Maps OÜ, the fork of Maps.me).

I repeat: There is no point investing time and effort in this new project if in the future the new founder can sell everything without needing votes for it and without needing to satisfy anyone here. He puts the money in his pocket and everything is fine. Please, don't make that mistake again.We shouldn't trust anyone, so there must be legal barriers to prevent what happened with Simple Mobile Tools happen here again in the future.

White splash screen for light themed apps

This would apply to all the fossify apps that are forks of SMT. Posting it here since it's the only one on f-droid at the moment.

The launch splash screen is black regardless of theme. Light themed apps should have a white splash screen.

Raised issue here in general as requested.
Splash screens shouldn't be black for light themes.

Project website

@ronniedroid Hey naveensingh liked your comment, so maybe you may try something?
First we should do disscussion about ideas. So you or someone else doesnt do something, that we wouldnt use :)

Would static website be enough? With GoHugo or Jekyll? Or?

It should be Open source.
Homepage/Index page with all the apps, links to their github, f-drod, google play.
Support/donate page with Support/donate options (+ and their fees, so supporters could choose)
Links to social media + github, f-drod, google play in footer.
With blog with rss.
More languages support with Hosted Weblate.

Something like the last one. https://www.simplemobiletools.com

Or do you have better ideas? Please share them. :)

New filter type, Nice to have for Contact list

Hello,

The example :
For the global contact list, I'd like to view all contact "friend" group, "family" group, but no contact from "medical" group.
This will be very usefull to have a filter for global list.

[Rewrite] Top bar should be more minimal

Top bars right now seems too much cluttered
For example in sms messenger, flashlight, voice recorder, clock there are 3 icons, when one should be enought
In others there could maybe be more minimalistic top bar too

Spam folder for fossify messages

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs), in the README and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report may get dismissed otherwise.
  • This issue contains only one feature request.
  • I optionally donated to support the Fossify mission.

Which apps should have this feature?

Messages

Feature description

I know its an initial release and i am sorry to requesting a feature too early, Only issue with the fossify sms is there isn't a spam folder or a way to retrieve accidentally blocked sms

Why do you want this feature?

I accidentally blocked an sms , i couldn't find an spam folder or anything like that, as a temporary solution i installed another sms app and retrieve that blocked message from there

Additional information

No response

Linux support

Is this new suite of apps going to be linux compatible? Believe it or not, Linux has no foss voice recorders that aren't ancient or feature barren.

Will be the Thank-You app still needed?

The Thank-You app from the original repo/suite is intended to unlock all features (some features were only enabled in the paid versions from the Play Store). Correct me if I'm mistaken.

Will FossifyOrg keep the same approach or will definitely go completely FOSS?
If yes, I think the Thank-You app could be dropped / merged in the Common library.

PS: can't find the Issues tab in the Thank-You repo.

Option to choose custom icon for app

Pretty self explanatory, like in signal app user can change app icon and even app name from a bunch of options. So if possible option to choose app icon from icon pack will be a fine addition and also option to change app name like change the form "Phone" to user defined name "Dialer" or anything else for that matter.

Bug (Messages) : Theme isn't applying on the Action Bar.

Checklist

  • [✅] I can reproduce the bug with the latest version.
  • [✅] I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
  • [✅] I have read the FAQ and my problem isn't listed.
  • [✅] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • [✅] This issue contains only one bug.
  • [✅] I have read and understood the contribution guidelines.

Describe the bug
Whenever you long-press on a message or conversation, an Action Bar appears. But the problem is that the bar doesn't follow the custom theme chosen by the user. So, please fix this.

To Reproduce
Steps to reproduce the behavior:

  1. Open Fossify Messages app.
  2. Long-press on any conversation, then notice the Action Bar.
  3. Open any conversation & long-press any message, then notice the Action Bar.

Note: Before following above steps, you should already be using a pure black AMOLED Theme like me.

Expected behavior
Whatever colour user has chosen in "Background Colour" & "Primary Colour" should also get applied to the Action Bar.

Screenshots
Screenshot_2024-01-23-07-24-50-57_f3369ad6253aa3dfe04568d105f6ea48
Screenshot_2024-01-23-07-26-42-19_f3369ad6253aa3dfe04568d105f6ea48

Device info (please complete the following information):

  • Model: Realme 7 Pro
  • OS: Android 12 (skin name is RUI 3.0)
  • App version: v1.0.0

Additional context
Not really, wrote everything above.

Refunds for SelloutMobileTools

Dont forget to get your refund. As per the almighty Tibors own words in his 11 reasons why our apps rock

"10. Affordable

Some of them are free, some of them are paid. That's because the development takes time and money, so we have to make money in some way. As the apps have no ads and they aren't stealing any of your data either, the best way to earn something was simply making them paid. That also makes our business model really clear. You just have to pay a small sum and you can use the apps forever. It is a one time payment, you will never have to pay for them again. Not even once you get a new device. If you want a refund, just contact us anytime at [email protected] and you will get it. No questions asked."

https://www.reddit.com/r/SimpleMobileTools/comments/f2uo1s/11_reasons_why_our_apps_rock/?sort=new

You can use your credit card to chargeback or paypal dispute if this sellout to a jewish ad company refuses.

Stripe support for Liberapay

As of now the Liberapay payment processto Fossify is only available through Paypal processing. It would be nice if payments through stripe also would be available.

Liberapay supports Paypal and Stripe.

[Migration] Compose-first approach (all new layouts and long-term migration)

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I have read the FAQ and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.

Current code base is 100% Kotlin, but still uses the kinda-legacy Android layout views system.

Describe the solution you'd like

Using Jetpack Compose would ease working with layout options (e.g. Adapters/Recyclers, views designs FossifyOrg/Gallery#13) and allows dropping the use of some dependencies (e.g. FossifyOrg/Gallery#36).

Migrating the whole code at once is a relatively big project with a lot of sub-tasks (started to get the hang of it, after doing this for 3 projects). That's why it'd make sense at first to only (re)implement anything in Compose when it's being added or touched/modified.

If someone is willing to take on such task, I'm gladly available for discussion.

Update bottom navigation bar to Material Design 3

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs), in the README and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report may get dismissed otherwise.
  • This issue contains only one feature request.
  • I optionally donated to support the Fossify mission.

Which apps should have this feature?

All Fossify Apps

Feature description

Update the bottom navigation bar to follow Material Design 3 navigation bar styling.

Why do you want this feature?

The apps already use Material Design 3 for the most part but the bottom navigation bar still looks outdated.

Additional information

No response

Switching between certain color themes breaks the app

Checklist

  • I can reproduce the bug with the latest version.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
  • I have read the FAQ and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Describe the bug
When switching between certain app themes, the app crashes and it cannot be started anymore. Tapping on the app icon only opens the app settings, but the 'open' button is missing.

I could reproduce this behavior in both the calendar and gallery app when switching from the 'dark red' theme to the 'white' theme.

To Reproduce
Steps to reproduce the behavior:

  1. Go to settings -> customize colors
  2. Select the 'dark red' theme
  3. Go back to the app's main screen
  4. Go to settings -> customize colors
  5. Select the 'white' theme
  6. Go back to the app's main screen
  7. The app closes/crashes.
  8. Try reopening the app.
  9. The app's android settings are opened, but there is no 'open' button.

Expected behavior
The app opens normally no matter which theme is selected.

Screenshots
N/A

Device info (please complete the following information):

  • Model: Google Pixel 6a
  • OS: Android 14 (Graphene OS)
  • App Version: gallery (1.1.0) and calendar (1.0.2)

Additional context
I tried clearing both storage and cache, but that didn't resolve the issue. I had to completely reinstall the apps to make them work again.

Fossify Contact/Phone Custom Ring Tone does not work

Checklist

  • I can reproduce the bug with the latest versions.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs), in the README and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report may get dismissed otherwise.
  • This issue contains only one bug.

Affected Android/Custom ROM version

Android 13

Affected device model

Moto g73

How did you install the apps?

F-Droid / IzzyOnDroid

Which apps are affected?

Contacts, Phone

Steps to reproduce the bug

Add the Custom Ringtone Field in Fossify Contacts App
Select a ringtone from phone's default list of ring tone OR from Ringtone Folder (Path=/Storage/emulated/0/Ringtones/". Custom ringtone audio file type is MP3.

Expected behavior

Custom Ring Tone should be ringing when contact calling in.

Actual behavior

Custom Ring Tone is NOT ringing when contact calling in.

Screenshots/Screen recordings

Is NOT applicable

Additional information

ADD the Same contact details also in android NATIVE CONTACTS APP. And now, the custom tone ringing when call comes in.

Long file paths are not properly displayed

Hi !
I first reported this bug in the Simple File Manager repo #758 but I prefer to republish it in general issues as I know the problem already affects Fossify Gallery.

When browsing the file explorer, a long file path can be superimposed on the "internal" or "SD card" button, making it difficult to click. This also happens when you select a destination to copy or move file (e.g. in the gallery when you are moving a photo).

I can't support you financially for now so I hope this will help you a little. Thank you for your work ;)

[Unintentional, please ignore]

Sorry, accidentally posted, please ignore (was trying to check if GitHub can display similar issues when creating a new issue; doesn't appear to be possible).

Remove "forked from" property from all repos

Please remove "forked from" property from all repos. It might not be the case (anymore) - i havent tested - but as far as i know when original repo is removed and/or privatised on github the maintainer of that repo has the ability to remove all forks
image

Detach forks from SimpleMobileTools

Currently the repositories (e.g. FossifyOrg/File-Manager) are "forks" of the corresponding SimpleMobileTools repositories.

There are at least a couple of issues with this:

  1. New pull requests will by default target the upstream repository (SimpleMobileTools)
  2. Forks are not shown in the GitHub search results.

Please consider detaching the forks. It can be done through this support page (using a chatbot apparently).

Black theme for night mode in Material You mode

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs), in the README and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report may get dismissed otherwise.
  • This issue contains only one feature request.
  • I optionally donated to support the Fossify mission.

Which apps should have this feature?

All Fossify Apps

Feature description

Have the choice of having the material you theme along with the black theme when the device is in dark mode

Why do you want this feature?

Black theme is consume less battery on OLED phones, and can't actually be enabled with the Material You theme

Additional information

No response

Change the Shape of the Search Box Background

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I have read the FAQ and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
This is more of an annoyance. The Search Box Background has no corners, it ends in semicircles (in most of the apps). I don't like this!

Describe the solution you'd like
I would like for the Search Box Background to have round corners.

Describe alternatives you've considered
I have tried making the background "disappear" by setting the app Primary Color to be the same as the Background Color but then the app Main Tab "disappears" into the Tab Bar in apps where there is one.

Additional context
Here's an example of how I would like the Search Box to look:

Screenshot_2024-01-17-17-07-33-437_com pcloud pcloud_1

Thanks for reading this! : )

Organization and app name

The project name (FossifyX) is not set in stone either, if you guys have an idea for a better name, please let me know.

Mascot

Like all FLOSS projects of this caliber, we need a mascot and then we need to PR it to SuperTuxKart and SuperTuxParty. We'll also need a short leitmotif.

  1. Leitmotif
  2. Rigged Blender Model (for games)
  3. Icon
  4. A name

If you have suggestions for the mascot, please post them here. A crude drawing is all that's needed for the community to vote on them. Look at the cast of SuperTuxKart for inspiration / reference for what FLOSS mascots are like and how they're stylised.

Default Colour Scheme for Icons and App Theming

To differentiate this project from the original simple tools, the default color scheme for the icons and in app theme should probably be different.
This was my first idea (Text:#098D9C, Backround:#B5F774).
mic_icon

F-Droid link to Fossify apps

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs), in the README and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report may get dismissed otherwise.
  • This issue contains only one feature request.
  • I optionally donated to support the Fossify mission.

Which apps should have this feature?

No response

Feature description

Why do you want this feature?

Because it's useful.

Additional information

No response

Replace SMS Messenger by a fork of QKSMS?

Hi,

when deciding which apps to maintain I was wondering about switching from the Simple SMS Messenger to a fork of QKSMS:
https://github.com/moezbhatti/qksms

In my opinion it is a much better SMS app and its development should continue after it has been abandoned by its dev.

There is a recent attempt to fork it and maintain here as Quik:
https://github.com/octoshrimpy/quik

Perhaps you could join efforts with https://github.com/octoshrimpy and together continue its development as a new SMS app in the suite?

Maintaining import compatibility

Since this is starting off as a mirror of the original apps, data and settings exports from SMT to FossifyOrg will work. However, some features may eventually require breaking compatibility. Has there been any discussion on what to do with this situation? There are multiple options:

  1. Ignore and break compatibility whenever it comes up.
  2. Maintain compatibility for a certain reasonable period (a few months? a year?) so that people migrating from SMT won't be left stranded.
  3. Maintain permanent compatibility via a legacy import of sorts for all eternity.

Option 2 seems like the most workable, though of course 3 is the most ideal choice.

Improving the project name

Fossify? Really? Coming fresh from Brodie's video about the project, there are some other, more clever names you could had used. (BTW appreciate the effort, just a little gentle ribbing and stoking the fires of passion to hopefully give this project a more punchy name.)

PureDroid / Pure Tools were already discussed elsewhere, why not CleanDroid or Clean Tools? The collective project as CleanSuite? Or maybe, even better considering the moral of SMT's story was a fable of commercialisation, and that this name also contains all letters for the Android Open Source Project (AOSP), AesopTools.

Throw your hat in the ring and let's see what sticks.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.